dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-33180

HIGH · 7.5 CVSS v3.1 Published 2026-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HAPI FHIR's internal HTTP client improperly forwards custom headers to redirect destination hosts. When the server returns a 30X redirect, the same headers (potentially containing authentication tokens, cookies, or other sensitive data) are sent to the new host specified in the Location header, leaking sensitive information to unintended domains.

MitigationUpgrade HAPI FHIR to version 6.9.0 or later. Conduct thorough testing to verify that redirect handling works correctly and that no sensitive headers are leaked to third-party domains.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify HAPI FHIR installation and version
    Locate the HAPI FHIR library in your project dependencies (Maven pom.xml, Gradle build file, or JAR manifest). Check the declared version attribute against the affected range (versions prior to 6.9.0).
    Affected if The installed version is lower than 6.9.0.
  2. Confirm internal HTTP client is in use
    Review your application code to determine if it uses HAPI FHIR's built-in HTTP client (such as GenericClient or the RestfulClient) to make outbound API calls. Search for imports from ca.uhn.fhir.rest.client and usage of RestfulClient or similar client classes.
    Affected if Your code instantiates and uses HAPI FHIR's internal RestfulClient or GenericClient to make HTTP requests.
  3. Check if redirect handling is enabled
    Inspect the client configuration for redirect behavior. Look for settings related to followRedirects, handleLocationRedirects, or similar properties in your client setup code or configuration files. Default behavior in older versions follows 30X redirects automatically.
    Affected if Redirect handling is enabled or left at default (which allows automatic redirects).
  4. Determine if sensitive headers are sent with requests
    Review the HTTP requests made through the HAPI client to identify if Authorization headers, cookies, or custom authentication tokens are included. Check the client invocation code for header additions using withHeaders, withAuthorization, or cookie parameters.
    Affected if Your client sends authentication tokens, cookies, or other sensitive data in request headers to endpoints that could trigger a redirect.

You are affected if HAPI FHIR version is below 6.9.0 AND your application uses the internal HTTP client with redirect-enabled requests that carry sensitive headers like auth tokens or cookies.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HAPI FHIR to version 6.9.0 or later. Conduct thorough testing to verify that redirect handling works correctly and that no sensitive headers are leaked to third-party domains.

Recommended fix High confidence

6.9.0

  1. Upgrade HAPI FHIR to version 6.9.0 or later
  2. Verify the upgrade by checking the library version in your project dependencies

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33180 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33180 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data