Skip to content
Fencer Vulns
high 8.2

CVE-2026-33180 json

HAPI FHIR HTTP authentication leak in redirects

published 2026-03-18 7 mo ago modified 2026-07-15 3 mo ago also EUVD-2026-13828 , GHSA-p7m9-v2cm-2h7m

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven 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
  • ca.uhn.hapi.fhir org.hl7.fhir.core 6.9.0
  • hapifhir hl7_fhir_core 6.9.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-33180 updated cvss 8.2

HAPI FHIR: hapifhir/org.hl7.fhir.core: HAPI FHIR: Information disclosure and potential impersonation via HTTP redirects sending sensitive headers

  • Red Hat Fuse 7 org.hl7.fhir.convertors, org.hl7.fhir.validation, org.hl7.fhir.validation.cli, ca.uhn.hapi.fhir-org.hl7.fhir.core
    affected: workaround, no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
7 mo ago

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CISA ADP 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven ca.uhn.hapi.fhir:org.hl7.fhir.utilities
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.convertors
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu2
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu3
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.model
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.r4
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.r4b
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.r5
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.validation
<6.9.0
6.9.0
maven ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli
<6.9.0
6.9.0

Affected products

  • hapifhir org.hl7.fhir.core
  • Red Hat Red Hat Fuse 7

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-201 Insertion of Sensitive Information Into Sent Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.