CVE-2026-34360 Overview
CVE-2026-34360 is a Server-Side Request Forgery (SSRF) vulnerability affecting HAPI FHIR, a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to version 6.9.4, the /loadIG HTTP endpoint in the FHIR Validator HTTP service accepts a user-supplied URL via JSON body and makes server-side HTTP requests to it without any hostname, scheme, or domain validation. This allows an unauthenticated attacker with network access to the validator to probe internal network services, cloud metadata endpoints, and map network topology through error-based information leakage.
Critical Impact
Unauthenticated attackers can leverage this SSRF vulnerability to perform internal network reconnaissance, access cloud metadata services, and potentially exfiltrate sensitive configuration data from healthcare infrastructure environments.
Affected Products
- HAPI FHIR versions prior to 6.9.4
- FHIR Validator HTTP service with /loadIG endpoint exposed
- Healthcare interoperability systems using vulnerable HAPI FHIR implementations
Discovery Timeline
- 2026-03-31 - CVE-2026-34360 published to NVD
- 2026-04-01 - Last updated in NVD database
Technical Details for CVE-2026-34360
Vulnerability Analysis
This vulnerability is classified as CWE-918 (Server-Side Request Forgery). The FHIR Validator HTTP service exposes the /loadIG endpoint which is designed to load Implementation Guides from external sources. However, the endpoint fails to implement proper validation of user-supplied URLs before making outbound HTTP requests.
The core issue lies in the lack of input validation on the URL parameter passed via the JSON request body. The application does not verify the hostname, scheme, or domain of the requested URL, allowing attackers to specify arbitrary destinations including internal network addresses, localhost services, and cloud provider metadata endpoints (such as 169.254.169.254 on AWS, GCP, and Azure).
When the explore=true parameter is set (which is the default behavior for this code path), each malicious request triggers multiple outbound HTTP calls. This amplification significantly enhances an attacker's reconnaissance capability, allowing them to rapidly scan internal networks and enumerate available services.
Root Cause
The root cause of CVE-2026-34360 is the absence of URL validation and allowlist-based filtering in the /loadIG endpoint. The application trusts user-supplied URLs without verifying that they point to legitimate, external FHIR resources. This violates the security principle of validating all user input, especially when that input is used to initiate network connections.
The vulnerability is exacerbated by the default explore=true behavior, which was likely designed for legitimate use cases but inadvertently amplifies the impact of SSRF attacks by generating multiple outbound requests per single malicious input.
Attack Vector
An attacker can exploit this vulnerability by sending crafted HTTP requests to the /loadIG endpoint with malicious URLs in the JSON body. The attack vector is network-based and requires no authentication, making it particularly dangerous in environments where the FHIR Validator service is exposed to untrusted networks.
Exploitation scenarios include:
- Cloud Metadata Access: Targeting cloud instance metadata endpoints to retrieve IAM credentials, API tokens, and instance configuration data
- Internal Network Scanning: Probing internal IP ranges to discover running services, open ports, and network topology
- Service Enumeration: Leveraging error-based information leakage to identify internal service types and versions
- Data Exfiltration: Accessing internal APIs or databases that may be reachable from the FHIR Validator service
The vulnerability is particularly concerning in healthcare environments where FHIR services may have access to sensitive patient data or critical infrastructure systems. For detailed technical information, refer to the GitHub Security Advisory.
Detection Methods for CVE-2026-34360
Indicators of Compromise
- Unusual outbound HTTP requests from FHIR Validator services to internal IP addresses (e.g., 10.x.x.x, 172.16.x.x, 192.168.x.x)
- Requests to cloud metadata endpoints such as 169.254.169.254 originating from the validator service
- High volume of requests to the /loadIG endpoint from single source IPs
- Error logs indicating connection failures to internal network addresses
Detection Strategies
- Implement network monitoring to detect outbound connections from FHIR Validator services to non-standard destinations
- Configure web application firewall (WAF) rules to inspect JSON body parameters for internal IP addresses and metadata endpoint URLs
- Enable detailed access logging on the /loadIG endpoint to track all URL requests
- Deploy intrusion detection systems (IDS) with signatures for common SSRF payloads targeting cloud metadata services
Monitoring Recommendations
- Monitor FHIR Validator service logs for requests containing RFC 1918 private IP addresses or localhost references
- Set up alerts for outbound connection attempts to well-known cloud metadata IP addresses
- Track error rates on the /loadIG endpoint as SSRF reconnaissance often generates numerous failed connection attempts
- Implement network segmentation monitoring to detect lateral movement attempts following successful reconnaissance
How to Mitigate CVE-2026-34360
Immediate Actions Required
- Upgrade HAPI FHIR to version 6.9.4 or later immediately
- Restrict network access to the /loadIG endpoint to trusted sources only
- Implement egress filtering to prevent the FHIR Validator service from making connections to internal networks
- Review access logs for evidence of exploitation attempts
Patch Information
The vulnerability has been addressed in HAPI FHIR version 6.9.4. Organizations should update to this version or later to remediate the SSRF vulnerability. The patch implements proper URL validation to prevent requests to internal network addresses and cloud metadata endpoints. For complete patch details, refer to the GitHub Security Advisory.
Workarounds
- Disable or restrict access to the /loadIG endpoint if it is not required for operations
- Implement network-level egress filtering to block outbound connections from the FHIR Validator to internal networks and cloud metadata endpoints
- Deploy a reverse proxy with URL validation capabilities in front of the FHIR Validator service
- Use network segmentation to isolate the FHIR Validator from sensitive internal resources
# Example: iptables rules to block outbound requests to cloud metadata endpoints
iptables -A OUTPUT -d 169.254.169.254 -j DROP
iptables -A OUTPUT -d 10.0.0.0/8 -j DROP
iptables -A OUTPUT -d 172.16.0.0/12 -j DROP
iptables -A OUTPUT -d 192.168.0.0/16 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
