High (7.0) in dadrus heimdall. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in https://github.com/dadrus/heimdall 0.17.17.
Heimdall is a cloud native Identity Aware Proxy and Access Control Decision service. Prior to version 0.17.17, when the trusted_proxies option is configured, heimdall extracts client IP addresses from the Forwarded (for= parameter) and X-Forwarded-For headers and exposes them as Request.ClientIPAddresses to the rule pipeline. However, extracted values are not validated to be syntactically valid IP addresses. Arbitrary strings, malformed IP literals, and RFC 7239 unknown values and obfuscated identifiers are accepted without further checks. In addition, the Forwarded header parser splits on , and ; without accounting for RFC 7239 quoted strings, which can cause a single quoted value to be parsed as multiple entries, with fragments — including trailing quote characters — treated as independent addresses. This issue has been patched in version 0.17.17.
0.3%(unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · 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-20Improper Input Validation CWE-116Improper Encoding or Escaping of Output CWE-290Authentication Bypass by Spoofing
Show the promptExplain CVE-2026-57210 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-57210?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-57210?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-57210 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.
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: SUSE · openSUSE.
Attack patterns (CAPEC)
CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High
CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-290, CWE-20 (51).