NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2026-33180 — org.hl7.fhir.utilities

HIGH

CVE-2026-33180 is a high-severity (CVSS 7.5) Information Exposure vulnerability in ca.uhn.hapi.fhir:org.hl7.fhir.utilities. A fix is available for ca.uhn.hapi.fhir:org.hl7.fhir.utilities — see the affected versions and patch details below.

HAPI FHIR HTTP authentication leak in redirects

Also known asGHSA-p7m9-v2cm-2h7m
Published
Updated
Affected
12 pkgs
Patched
12 / 12
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33180.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk+0.01%
Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk
0.00%0.32%0.65%0.97%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

12 pkgs affected
☕ca.uhn.hapi.fhir:org.hl7.fhir.utilities☕ca.uhn.hapi.fhir:org.hl7.fhir.convertors☕ca.uhn.hapi.fhir:org.hl7.fhir.dstu2☕ca.uhn.hapi.fhir:org.hl7.fhir.dstu3☕ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support☕ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may☕ca.uhn.hapi.fhir:org.hl7.fhir.model☕ca.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.0ca.uhn.hapi.fhir:org.hl7.fhir.utilities:6.9.0
☕Mavenca.uhn.hapi.fhir:org.hl7.fhir.convertorsall versions6.9.0ca.uhn.hapi.fhir:org.hl7.fhir.convertors:6.9.0
☕Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu2all versions6.9.0ca.uhn.hapi.fhir:org.hl7.fhir.dstu2:6.9.0
☕Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu3all versions6.9.0ca.uhn.hapi.fhir:org.hl7.fhir.dstu3:6.9.0
☕Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu3.supportall versions6.9.0ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support:6.9.0
☕Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu2016mayall versions6.9.0ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may:6.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Source: Red Hat security advisory for CVE-2026-33180 (CC BY 4.0)

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?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-33180: org.hl7.fhir.utilities — Fixed in 6.9.0