Skip to content

HAPI FHIR HTTP authentication leak in redirects

Critical severity GitHub Reviewed Published Mar 17, 2026 in hapifhir/org.hl7.fhir.core • Updated Mar 18, 2026

Package

maven ca.uhn.hapi.fhir:org.hl7.fhir.convertors (Maven)

Affected versions

< 6.9.0

Patched versions

6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.model (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.r4 (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.r4b (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.r5 (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.utilities (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.validation (Maven)
< 6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli (Maven)
< 6.9.0
6.9.0

Description

Impact

When setting headers in HTTP requests, the internal HTTP client sends headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the Location: response header value.

Sending the same set of headers to subsequent hosts is a problem as this header often contains privacy sensitive information or data that could allow others to impersonate the client's request.

Patches

This issue has been patched in release 6.8.3

Workarounds

None.

References

@dotasek dotasek published to hapifhir/org.hl7.fhir.core Mar 17, 2026
Published to the GitHub Advisory Database Mar 18, 2026
Reviewed Mar 18, 2026
Last updated Mar 18, 2026

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

CVE ID

CVE-2026-33180

GHSA ID

GHSA-p7m9-v2cm-2h7m

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.