Security readout for executives and security teams
Plain-English summary
HAPI FHIR versions before 6.9.0 can leak sensitive HTTP headers during redirects. If a FHIR client follows a redirect to another host, authentication or privacy-sensitive headers may be sent to that new host, creating credential misuse or request impersonation risk.
Executive priority
Treat as high priority for healthcare integrations that use FHIR clients with credentials, tokens, or sensitive request headers. Upgrade promptly because the advisory names no workaround.
Technical view
The internal HTTP client in org.hl7.fhir.core forwards the same request headers after receiving a 30X redirect, including to the host named in the Location header. The flaw affects versions before 6.9.0 and is patched in 6.9.0.
Likely exposure
Exposure is likely in Java applications using HAPI FHIR org.hl7.fhir.core before 6.9.0 where outbound HTTP requests include sensitive headers and redirects are followed.
Exploitation context
The provided sources do not indicate active exploitation, and KEV status is false. Practical impact depends on whether redirected requests can reach a different or attacker-controlled host while carrying sensitive headers.
Researcher notes
This is a confidentiality and integrity issue, not an availability issue. Validation should focus on dependency version, redirect-following behavior, sensitive header use, and whether redirects can cross trust boundaries.
Mitigation direction
- Upgrade org.hl7.fhir.core and related HAPI FHIR dependencies to version 6.9.0 or later.
- Check vendor and distribution guidance, including Red Hat advisories, for packaged dependency status.
- Review outbound FHIR client configurations that follow redirects with authentication or privacy-sensitive headers.
- Rotate exposed credentials if logs or monitoring indicate sensitive headers reached unintended hosts.
Validation and detection
- Inventory applications using HAPI FHIR org.hl7.fhir.core and identify versions below 6.9.0.
- Review dependency lockfiles, SBOMs, and runtime artifacts for vulnerable HAPI FHIR core versions.
- Confirm upgraded builds resolve org.hl7.fhir.core to 6.9.0 or later.
- Inspect telemetry for unexpected redirect destinations from FHIR client traffic.
- Verify no sensitive headers are forwarded across host boundaries after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-201: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-33180 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N3.94.2redhat-SADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6GitHub_MVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-20T23:02:53.630Z: Reported to Red Hat.
- 2026-03-20T22:19:59.636Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/hapifhir/org.hl7.fhir.core/security/advisories/GHSA-p7m9-v2cm-2h7mCVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-33180CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2449841CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33180.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Insertion of Sensitive Information Into Sent Data
Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.