Vulnerabilities in pkg:golang/https://github.com/dadrus/heimdall
PACKAGECVE-2026-57210 is a HIGH ip spoofing vulnerability (CWE-116: Improper Encoding or Escaping of Output) affecting Heimdall libraries in the Go ecosystem. The issue involves ip spoofing via unvalidated forwarding headers. Remediation is available by upgrading affected packages to version 0.17.17.
pkg:golang/https://github.com/dadrus/heimdall
Vulnerability advisories affecting package pkg:golang/https://github.com/dadrus/heimdall. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-38x9-25wx-7fg2 | CVE-2026-57210 | HIGH | Heimdall: IP Spoofing via Unvalidated Forwarding Headers |
CVE-2026-57210 at a Glance
How to Fix CVE-2026-57210
To remediate this vulnerability, upgrade all affected Heimdall dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>https</groupId>
<artifactId>//github.com/dadrus/heimdall</artifactId>
<version>0.17.17</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for https://github.com/dadrus/heimdall
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-57210, inspect your project dependencies for Heimdall:
inspect dependencies for https://github.com/dadrus/heimdall
Analyze the terminal output to locate any version of Heimdall in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.17.17), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-116: Improper Encoding or Escaping of Output, where the product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. as a result, the intended structure of the message is not preserved. In Heimdall, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-57210 Affected Heimdall Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
https://github.com/dadrus/heimdall
|
Go |
< 0.17.17
|
0.17.17
|
References
Frequently Asked Questions
What is CVE-2026-57210?
Which Heimdall versions are affected?
What version fixes CVE-2026-57210?
Is //github.com/dadrus/heimdall affected?
What CWE is associated with CVE-2026-57210?
How can I check Go dependencies for CVE-2026-57210?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-38x9-25wx-7fg2",
"modified" : "2026-07-20T21:28:51Z",
"published" : "2026-06-18T14:24:37Z",
"aliases" : [ "CVE-2026-57210" ],
"summary" : "Heimdall: IP Spoofing via Unvalidated Forwarding Headers",
"details" : "### Summary\n\nWhen 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.\nIn 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.\n\n### Impact\n\n`Request.ClientIPAddresses` is available to all pipeline mechanisms. Its contents can therefore influence rule evaluation in deployments where rules reference this property — for example, in a `CEL` authorizer that checks whether a request originates from a trusted IP range using the `networks()` function, or in a `Remote` authorizer that forwards the client IP as part of its payload to an external authorization system. Whether and how `Request.ClientIPAddresses` is used is entirely determined by the rule configuration.\n\nAdditionally, in proxy mode, `Request.ClientIPAddresses` is used directly to construct the `X-Forwarded-For` and `Forwarded` headers forwarded to upstream services. Injected or malformed values are therefore propagated to upstream services unchanged.\n\n### Attack Scenarios\n\nAll scenarios require that `trusted_proxies` is configured. If this option is not set, heimdall ignores forwarding headers entirely, and this vulnerability is not exploitable. Scenarios A and C (see below) additionally require that rules reference `Request.ClientIPAddresses` in their pipeline.\n\n#### Scenario A – Manipulation of rule evaluation\n\nAn attacker who can influence forwarding headers — either by connecting directly to heimdall or through a proxy that does not sanitize these headers — can inject arbitrary values into `Request.ClientIPAddresses`. In deployments where a rule references this property (e.g. to restrict access to specific IP ranges), this may allow an attacker to bypass the intended access control logic.\n\n#### Scenario B – IP spoofing against upstream services (proxy mode)\n\nIn proxy mode, injected or malformed values in `Request.ClientIPAddresses` are written unchanged into the `X-Forwarded-For` header sent to upstream services. Upstream services that trust this header may therefore receive and act on attacker-controlled IP values.\n\n#### Scenario C – Malformed entries via quoted-string misparse\n\nA `Forwarded` header containing a quoted value with embedded delimiters (`,` or `;`) is misparsed, producing unintended additional entries in `Request.ClientIPAddresses`, including malformed fragments with trailing quote characters.\n\n### Workarounds\n\n* Ensure at the network level that only trusted proxies can communicate directly with heimdall.\n* Ensure that the proxy forwarding the requests to heimdall sanitizes or overrides (not merely appends to) `Forwarded` or `X-Forwarded-For` headers before forwarding them.\n* Avoid relying on `Request.ClientIPAddresses` for security-sensitive decisions until patched",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "https://github.com/dadrus/heimdall"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.17.17"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.17.16"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/dadrus/heimdall/security/advisories/GHSA-38x9-25wx-7fg2"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/dadrus/heimdall"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-116", "CWE-20", "CWE-290" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-18T14:24:37Z",
"nvd_published_at" : null
}
}