CVE-2026-42274: Github.com/dadrus/heimdall Heimdall Has An Authorization Bypass Vulnerability

HIGH
Advisory Identifier: GHSA-3q34-rx83-r6mq
CWE-436 CWE-35
Published
Advisory Summary

CVE-2026-42274 is a HIGH heimdall has an authorization bypass vulnerability (CWE-436: Interpretation Conflict) affecting Github.com/dadrus/heimdall libraries in the Go ecosystem. The issue involves heimdall has an authorization bypass via path normalization mismatch. Remediation is available by upgrading affected packages to version 0.17.14.

CVE-2026-42274 at a Glance

CVE Identifier CVE-2026-42274
GHSA Identifier GHSA-3q34-rx83-r6mq
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-436: Interpretation Conflict
Affected Product Github.com/dadrus/heimdall
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-42274

To remediate this vulnerability, upgrade all affected Github.com/dadrus/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.

github.com/dadrus/heimdall fixed: 0.17.14
Upgrade github.com/dadrus/heimdall to 0.17.14
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 github.com/dadrus/heimdall

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-42274, inspect your project dependencies for Github.com/dadrus/heimdall:

inspect dependencies for github.com/dadrus/heimdall

Analyze the terminal output to locate any version of Github.com/dadrus/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.14), 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-436: Interpretation Conflict, where product a handles inputs or steps differently than product b, which causes a to perform incorrect actions based on its perception of b's state. In Github.com/dadrus/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 Heimdall performs rule matching on the raw (non-normalized) request path, while downstream components may normalize dot-segments according to [RFC 3986, Section 6.2.2.3](https://www.rfc-editor.org/rfc/rfc3986#section-6.2.2.3). This discrepancy can result in heimdall authorizing a request for one path (e.g., `/user/../admin`, or URL-encoded variants such as `/user/%2e%2e/admin` or `/user/%2e%2e%2fadmin`. The latter would require the `allow_encoded_slashes` option to be set to `on` or `no_decode`.) while the downstream ultimately processes a different, normalized path (`/admin`). ### Details This vulnerability can be exploited by an adversary if rule matching is performed using free (named or unnamed) wildcards without further constraints, as shown in the example snippets below. ```yaml id: rule-1 match: routes: - path: /user/** execute: # configured to require authentication and authorization # ... ``` ```yaml id: rule-2 match: routes: - path: /public/** execute: # configured to allow anonymous access # ... ``` If an adversary sends a request to `/public/../user/whatever`, rule-2 will be matched and executed. The downstream service may, however, normalize the request path and interpret it as `/user/whatever`. ### Impact Bypass of access control policies enforced by heimdall may lead to the following consequences: * Access to or modification of data that should be restricted * Invocation of functionality that is expected to require authentication or authorization * In certain configurations, escalation of privileges depending on the exposed functionality ### Workarounds * Normalize HTTP paths or reject HTTP paths containing relative path expressions in the layers in front of Heimdall - this is good practice anyway. Some proxies do that by default, such as Traefik; others, such as Envoy, require additional configuration (for Envoy see [`normalize_path`](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-normalize-path)). * Include the ID of the rule expected to be executed in the JWT issued by heimdall and check that value in the consuming project's service.

CVE-2026-42274 Affected Github.com/dadrus/heimdall Versions

1 component(s)
Fixed Versions:
0.17.14
Product / Package Ecosystem Affected Versions Fixed Version
github.com/dadrus/heimdall
Go
< 0.17.14
0.17.14

References

Frequently Asked Questions

What is CVE-2026-42274?
CVE-2026-42274 is a security vulnerability in Github.com/dadrus/heimdall involving Heimdall has an authorization bypass via path normalization mismatch under CWE-436: Interpretation Conflict.
Which Github.com/dadrus/heimdall versions are affected?
Affected versions include releases prior to 0.17.14 across affected packages: github.com/dadrus/heimdall.
What version fixes CVE-2026-42274?
Upgrading to 0.17.14 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/dadrus/heimdall affected?
Yes, github.com/dadrus/heimdall is affected in releases prior to 0.17.14. Upgrade your dependency to 0.17.14 or later.
What CWE is associated with CVE-2026-42274?
CVE-2026-42274 is classified under CWE-436: Interpretation Conflict (Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.).
How can I check Go dependencies for CVE-2026-42274?
Run the dependency tree command: 'inspect dependencies for 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-3q34-rx83-r6mq",
  "modified" : "2026-05-12T13:29:02Z",
  "published" : "2026-04-25T23:30:46Z",
  "aliases" : [ "CVE-2026-42274" ],
  "summary" : "Heimdall has an authorization bypass via path normalization mismatch",
  "details" : "### Summary\n\nHeimdall performs rule matching on the raw (non-normalized) request path, while downstream components may normalize dot-segments according to [RFC 3986, Section 6.2.2.3](https://www.rfc-editor.org/rfc/rfc3986#section-6.2.2.3). This discrepancy can result in heimdall authorizing a request for one path (e.g., `/user/../admin`, or URL-encoded variants such as `/user/%2e%2e/admin` or `/user/%2e%2e%2fadmin`. The latter would require the `allow_encoded_slashes` option to be set to `on` or `no_decode`.) while the downstream ultimately processes a different, normalized path (`/admin`).\n\n### Details\n\nThis vulnerability can be exploited by an adversary if rule matching is performed using free (named or unnamed) wildcards without further constraints, as shown in the example snippets below.\n\n```yaml\nid: rule-1\nmatch:\n  routes:\n    - path: /user/**\nexecute: # configured to require authentication and authorization\n  # ...\n```\n\n```yaml\nid: rule-2\nmatch:\n  routes:\n    - path: /public/**\nexecute: # configured to allow anonymous access\n  # ...\n```\n\nIf an adversary sends a request to `/public/../user/whatever`, rule-2 will be matched and executed. The downstream service may, however, normalize the request path and interpret it as `/user/whatever`.\n\n### Impact\n\nBypass of access control policies enforced by heimdall may lead to the following consequences:\n\n* Access to or modification of data that should be restricted\n* Invocation of functionality that is expected to require authentication or authorization\n* In certain configurations, escalation of privileges depending on the exposed functionality\n\n### Workarounds\n\n* Normalize HTTP paths or reject HTTP paths containing relative path expressions in the layers in front of Heimdall - this is good practice anyway. Some proxies do that by default, such as Traefik; others, such as Envoy, require additional configuration (for Envoy see [`normalize_path`](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-normalize-path)).\n* Include the ID of the rule expected to be executed in the JWT issued by heimdall and check that value in the consuming project's service.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/dadrus/heimdall"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.17.14"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/security/advisories/GHSA-3q34-rx83-r6mq"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42274"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/pull/3209"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/commit/b5dfa484b7a8c2ce6d8691c026f9da867719947a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/dadrus/heimdall"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/releases/tag/v0.17.14"
  }, {
    "type" : "WEB",
    "url" : "https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-normalize-path"
  }, {
    "type" : "WEB",
    "url" : "https://www.rfc-editor.org/rfc/rfc3986#section-6.2.2.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-35", "CWE-436" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-25T23:30:46Z",
    "nvd_published_at" : "2026-05-08T04:16:22Z"
  }
}