Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2026-33180

HIGH

HAPI FHIR HTTP authentication leak in redirects

Also known asGHSA-p7m9-v2cm-2h7m
Published
Mar 20, 2026
Updated
Apr 10, 2026
Affected
12 pkgs
Patched
12 / 12
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk15th percentile+0.20%
0.00%0.25%0.50%0.75%0.0%0.0%0.0%0.2%Apr 26Jun 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

12 pkgs affected
ca.uhn.hapi.fhir:org.hl7.fhir.utilitiesca.uhn.hapi.fhir:org.hl7.fhir.convertorsca.uhn.hapi.fhir:org.hl7.fhir.dstu2ca.uhn.hapi.fhir:org.hl7.fhir.dstu3ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.supportca.uhn.hapi.fhir:org.hl7.fhir.dstu2016mayca.uhn.hapi.fhir:org.hl7.fhir.modelca.uhn.hapi.fhir:org.hl7.fhir.r4+4 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to version 6.9.0, 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. This issue has been patched in release 6.9.0. No known workarounds are available.

Affected Packages

12 total 12 fixed
EcosystemPackageVulnerable rangeFix
Mavenca.uhn.hapi.fhir:org.hl7.fhir.utilitiesall versions6.9.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.convertorsall versions6.9.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu2all versions6.9.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu3all versions6.9.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu3.supportall versions6.9.0
Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu2016mayall versions6.9.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.uhn.hapi.fhir:org.hl7.fhir.utilities. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update ca.uhn.hapi.fhir:org.hl7.fhir.utilities to 6.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33180 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2026-33180 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-33180. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to version 6.9.0, 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. This issue
O3 Security · Impact-Aware SCA

Is CVE-2026-33180 in your dependencies?

O3 detects CVE-2026-33180 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.