Vulnerabilities in pkg:golang/https://github.com/dadrus/heimdall

PACKAGE
Advisory Identifier: GHSA-38x9-25wx-7fg2
Advisory Summary

CVE-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.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/https://github.com/dadrus/heimdall

1 Known Advisory Record(s)

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

CVE Identifier CVE-2026-57210
GHSA Identifier GHSA-38x9-25wx-7fg2
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-116: Improper Encoding or Escaping of Output
Affected Product Heimdall
Package Ecosystem Go
Published Date
Last Updated

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.

https://github.com/dadrus/heimdall fixed: 0.17.17
<dependency>
    <groupId>https</groupId>
    <artifactId>//github.com/dadrus/heimdall</artifactId>
    <version>0.17.17</version>
</dependency>
Verify Direct and Transitive Dependencies

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

### Summary 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. ### Impact `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. Additionally, 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. ### Attack Scenarios All 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. #### Scenario A – Manipulation of rule evaluation An 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. #### Scenario B – IP spoofing against upstream services (proxy mode) In 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. #### Scenario C – Malformed entries via quoted-string misparse A `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. ### Workarounds * Ensure at the network level that only trusted proxies can communicate directly with heimdall. * 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. * Avoid relying on `Request.ClientIPAddresses` for security-sensitive decisions until patched

CVE-2026-57210 Affected Heimdall Versions

1 component(s)
Fixed Versions:
0.17.17
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?
CVE-2026-57210 is a security vulnerability in Heimdall involving IP Spoofing via Unvalidated Forwarding Headers under CWE-116: Improper Encoding or Escaping of Output.
Which Heimdall versions are affected?
Affected versions include releases prior to 0.17.17 across affected packages: https://github.com/dadrus/heimdall.
What version fixes CVE-2026-57210?
Upgrading to 0.17.17 (or the latest patched release for your respective branch) resolves the vulnerability.
Is //github.com/dadrus/heimdall affected?
Yes, https://github.com/dadrus/heimdall is affected in releases prior to 0.17.17. Upgrade your dependency to 0.17.17 or later.
What CWE is associated with CVE-2026-57210?
CVE-2026-57210 is classified under CWE-116: Improper Encoding or Escaping of Output (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.).
How can I check Go dependencies for CVE-2026-57210?
Run the dependency tree command: 'inspect dependencies for https://github.com/dadrus/heimdall'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "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
  }
}