9.8
Critical
ca.uhn.hapi.fhir:org.hl7.fhir.utilities

CVE-2026-33180

CVE-2026-33180 is a critical-severity security vulnerability in ca.uhn.hapi.fhir:org.hl7.fhir.utilities (maven), affecting versions < 6.9.0. It is fixed in 6.9.0.

Key facts
CVSS score
9.8
Critical
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
ca.uhn.hapi.fhir:org.hl7.fhir.utilities
Fixed in
6.9.0
Disclosed
2026

Summary

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.

Impact

Severity and exposure

CVE-2026-33180 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (6.9.0). Upgrading removes the vulnerable code path.

Affected versions

maven

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

Security releases

  • ca.uhn.hapi.fhir:org.hl7.fhir.utilities → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.convertors → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.model → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.r4 → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.r4b → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.r5 → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.validation → 6.9.0 (maven)
  • ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli → 6.9.0 (maven)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-33180 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-33180 is reachable in your applications. Get a demo

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.utilities to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.convertors to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.model to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.r4 to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.r4b to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.r5 to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.validation to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli to 6.9.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-33180

What is CVE-2026-33180?

CVE-2026-33180 is a critical-severity security vulnerability in ca.uhn.hapi.fhir:org.hl7.fhir.utilities (maven), affecting versions < 6.9.0. It is fixed in 6.9.0.

How severe is CVE-2026-33180?

CVE-2026-33180 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2026-33180?
  • ca.uhn.hapi.fhir:org.hl7.fhir.utilities (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.convertors (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.model (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.r4 (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.r4b (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.r5 (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.validation (maven) (versions < 6.9.0)
  • ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli (maven) (versions < 6.9.0)
Is there a fix for CVE-2026-33180?

Yes. CVE-2026-33180 is fixed in 6.9.0. Upgrade to this version or later.

Is CVE-2026-33180 exploitable, and should I be worried?

Whether CVE-2026-33180 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-33180 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-33180?
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.utilities to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.convertors to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.model to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.r4 to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.r4b to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.r5 to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.validation to 6.9.0 or later
  • Upgrade ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli to 6.9.0 or later

Stop the waste.
Protect your environment with Kodem.