cve.bz

CVE-2026-57209 dadrus heimdall: Injection

7.0 highEPSS 0.5%Fix available

High (7.0) in dadrus heimdall. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/dadrus/heimdall 0.17.17.

On this page
Heimdall is a cloud native Identity Aware Proxy and Access Control Decision service. Prior to version 0.17.17, when Heimdall operates in proxy mode, it constructs the Forwarded HTTP header after executing the matched rule pipeline by inserting the incoming request's Host header value directly into the header string without sanitizing commas or semicolons. This allows an attacker to inject additional parameters into the Forwarded header, potentially spoofing IP addresses for upstream services. This issue has been patched in version 0.17.17.

Severity

CVSS 4.0

7.0 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-57209 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-57209?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-57209?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-57209 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
dadrus heimdall< 0.17.17

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4jgr-pg2m-m988Gogithub.com/dadrus/heimdall<0.17.170.17.17
GO-2026-5125Gogithub.com/dadrus/heimdall<0.17.170.17.17

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSETumbleweedheimdall2.2.2-1.1openSUSE-SU-2026:12397-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-74 (37), CWE-20 (51).

References

Check your stackJSON