CVE-2026-33180

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
17.9%
KEV
Not listed

Published

March 20, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 10, 2026
Patch available. Sources: github.
github Patch Available

HTTP authentication leak in redirects · Advisory · hapifhir/org.hl7.fhir.core · GitHub

https://github.com/hapifhir/org.hl7.fhir.core/security/advisories/GHSA-p7m9-v2cm-2h7m

Affected Packages

(12 across 1 ecosystem)
Maven(12)
PackageVulnerable rangeFixed inDependents
ca.uhn.hapi.fhir:org.hl7.fhir.convertors0.0.1 ... 6.8.2 (379 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.dstu20.0.1 ... 6.8.2 (379 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may0.0.1 ... 6.8.2 (379 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.dstu30.0.1 ... 6.8.2 (379 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support6.6.0 ... 6.8.2 (23 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.model6.5.25 ... 6.8.2 (27 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.r40.0.1 ... 6.8.2 (379 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.r4b5.6.100 ... 6.8.2 (252 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.r50.0.1 ... 6.8.2 (379 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.utilities0.0.1 ... 6.8.2 (379 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.validation0.0.1 ... 6.8.2 (379 versions)6.9.0—
ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli4.0.0 ... 5.0.0 (7 versions)6.9.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 05:32 UTCOSV refresh
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-24 14:05 UTCEPSS rescore
  24. 2026-06-23 21:33 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
Show 65 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 01:59 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-17 17:53 UTCEPSS rescore
  11. 2026-06-16 17:52 UTCEPSS rescore
  12. 2026-06-15 17:49 UTCEPSS rescore
  13. 2026-06-14 23:18 UTCEPSS rescore
  14. 2026-06-13 23:00 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 23:12 UTCEPSS rescore
  17. 2026-06-11 23:41 UTCEG score recompute
  18. 2026-06-11 14:00 UTCEPSS rescore
  19. 2026-06-10 22:18 UTCEPSS rescore
  20. 2026-06-10 17:38 UTCEG score recompute
  21. 2026-06-10 13:22 UTCEPSS rescore
  22. 2026-06-10 05:38 UTCEG score recompute
  23. 2026-06-09 16:21 UTCEG score recompute
  24. 2026-06-08 14:17 UTCEPSS rescore
  25. 2026-06-08 14:17 UTCEPSS rescore
  26. 2026-06-08 01:16 UTCEG score recompute
  27. 2026-06-07 15:25 UTCEPSS rescore
  28. 2026-06-07 15:25 UTCEPSS rescore
  29. 2026-06-07 15:25 UTCEPSS rescore
  30. 2026-06-07 13:49 UTCEG score recompute
  31. 2026-06-06 13:47 UTCEPSS rescore
  32. 2026-06-06 13:47 UTCEPSS rescore
  33. 2026-06-05 22:47 UTCEPSS rescore
  34. 2026-06-05 22:47 UTCEPSS rescore
  35. 2026-06-05 06:10 UTCEPSS rescore
  36. 2026-06-05 06:10 UTCEPSS rescore
  37. 2026-06-04 13:12 UTCEPSS rescore
  38. 2026-06-04 13:12 UTCEPSS rescore
  39. 2026-06-02 20:13 UTCEPSS rescore
  40. 2026-06-01 13:52 UTCEPSS rescore
  41. 2026-06-01 13:52 UTCEPSS rescore
  42. 2026-06-01 13:51 UTCEPSS rescore
  43. 2026-06-01 08:13 UTCOSV refresh
  44. 2026-05-31 22:30 UTCEPSS rescore
  45. 2026-05-31 22:30 UTCEPSS rescore
  46. 2026-05-31 00:16 UTCEPSS rescore
  47. 2026-05-31 00:16 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-29 13:44 UTCEPSS rescore
  50. 2026-05-29 13:44 UTCEPSS rescore
  51. 2026-05-28 13:44 UTCEPSS rescore
  52. 2026-05-28 13:44 UTCEPSS rescore
  53. 2026-05-28 13:44 UTCEPSS rescore
  54. 2026-05-27 13:40 UTCEPSS rescore
  55. 2026-05-27 13:40 UTCEPSS rescore
  56. 2026-05-27 13:40 UTCEPSS rescore
  57. 2026-05-26 13:44 UTCEPSS rescore
  58. 2026-05-26 07:18 UTCEPSS rescore
  59. 2026-05-26 07:18 UTCEPSS rescore
  60. 2026-05-23 00:09 UTCEG score recompute
  61. 2026-05-20 22:38 UTCEPSS rescore
  62. 2026-05-20 22:38 UTCEPSS rescore
  63. 2026-05-20 20:50 UTCEG score recompute
  64. 2026-05-20 11:22 UTCEPSS rescore
  65. 2026-05-20 11:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-33180?
CVE-2026-33180 is a high vulnerability published on March 20, 2026. 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…
When was CVE-2026-33180 disclosed?
CVE-2026-33180 was first published in the National Vulnerability Database on March 20, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33180 actively exploited?
CVE-2026-33180 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33180?
CVE-2026-33180 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33180?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33180, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33180

Explore →

Is Your Infrastructure Affected by CVE-2026-33180?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs