All reports
Critical

HAPI FHIR HTTP authentication leak in redirects

Affected versions

Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
< 6.9.0
Fixed version
6.9.0
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-33180

Probability of exploitation in the next 30 days: 0.31%

FIRST EPSS · 2026-11-21

Description

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.

Links

Credits

  • ElliotSilver