CVE-2026-42272: Heimdall Case-sensitive Handling Of URL-encoded Slashes Vulnerability

HIGH
Advisory Identifier: GHSA-43jv-5j4x-qv67
CWE-436 CWE-178
Published
Advisory Summary

CVE-2026-42272 is a HIGH case-sensitive handling of url-encoded slashes vulnerability (CWE-436: Interpretation Conflict) affecting Heimdall libraries in the Go ecosystem. The issue involves case-sensitive handling of url-encoded slashes may lead to inconsistent path interpretation. Remediation is available by upgrading affected packages to version 0.17.14.

CVE-2026-42272 at a Glance

CVE Identifier CVE-2026-42272
GHSA Identifier GHSA-43jv-5j4x-qv67
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-436: Interpretation Conflict
Affected Product Heimdall
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-42272

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.

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-42272, inspect your project dependencies for Heimdall:

inspect dependencies for 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.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 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 handles URL-encoded slashes (`%2F`) in a case-sensitive manner, while percent-encoding is defined to be case-insensitive. As a result, the lowercase equivalent (`%2f`) is not recognized and therefore not processed as expected when `allow_encoded_slashes` is set to `off` (the default setting). This discrepancy can lead to differences in how request paths are interpreted by heimdall and upstream components, which may result in authorization bypass. **Note:** The issue can only lead to unintended access if heimdall is configured with an "allow all" default rule. Since v0.16.0, heimdall enforces secure defaults and refuses to start with such a configuration unless this enforcement is explicitly disabled (e.g. via `--insecure-skip-secure-default-rule-enforcement` or the broader `--insecure` flag). ### Details Consider the following rule configuration: ```yaml id: rule-1 match: routes: - path: /admin/** execute: # configured to require authentication and authorization # ... ``` If an adversary sends a request such as `/admin%2fsecret`, neither is the above rule matched, nor is the request rejected (as would be expected when `allow_encoded_slashes` is set to `off`). Instead, the default rule (if configured) will be executed. If the configured default rule is overly permissive (e.g. allowing anonymous access), and the upstream service interprets `%2f` as a path separator, the request may ultimately be processed as `/admin/secret`. This results in the request being authorized based on a different path than the one processed by the upstream service, leading to authorization bypass. ### 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 * Developers should not use the `--insecure` or the `--insecure-skip-secure-default-rule-enforcement` flags and configure their default rule to implement "deny by default". * Reject HTTP paths containing encoded slashes in the layers in front of heimdall. Some proxies, like e.g., Traefik, do that by default. * Include the ID of the rule expected to be executed in the JWT issued by heimdall and verify that value in the project's service.

CVE-2026-42272 Affected 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-42272?
CVE-2026-42272 is a security vulnerability in Heimdall involving Case-sensitive handling of URL-encoded slashes may lead to inconsistent path interpretation under CWE-436: Interpretation Conflict.
Which 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-42272?
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-42272?
CVE-2026-42272 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-42272?
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-43jv-5j4x-qv67",
  "modified" : "2026-05-12T13:28:19Z",
  "published" : "2026-04-25T23:29:40Z",
  "aliases" : [ "CVE-2026-42272" ],
  "summary" : "Heimdall: Case-sensitive handling of URL-encoded slashes may lead to inconsistent path interpretation",
  "details" : "### Summary\n\nHeimdall handles URL-encoded slashes (`%2F`) in a case-sensitive manner, while percent-encoding is defined to be case-insensitive. As a result, the lowercase equivalent (`%2f`) is not recognized and therefore not processed as expected when `allow_encoded_slashes` is set to `off` (the default setting).\n\nThis discrepancy can lead to differences in how request paths are interpreted by heimdall and upstream components, which may result in authorization bypass.\n\n**Note:** The issue can only lead to unintended access if heimdall is configured with an \"allow all\" default rule. Since v0.16.0, heimdall enforces secure defaults and refuses to start with such a configuration unless this enforcement is explicitly disabled (e.g. via `--insecure-skip-secure-default-rule-enforcement` or the broader `--insecure` flag).\n\n### Details\n\nConsider the following rule configuration:\n\n```yaml\nid: rule-1\nmatch:\n  routes:\n    - path: /admin/**\nexecute: # configured to require authentication and authorization\n  # ...\n```\n\nIf an adversary sends a request such as `/admin%2fsecret`, neither is the above rule matched, nor is the request rejected (as would be expected when `allow_encoded_slashes` is set to `off`). Instead, the default rule (if configured) will be executed.\n\nIf the configured default rule is overly permissive (e.g. allowing anonymous access), and the upstream service interprets `%2f` as a path separator, the request may ultimately be processed as `/admin/secret`.\n\nThis results in the request being authorized based on a different path than the one processed by the upstream service, leading to authorization bypass.\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\n### Workarounds\n\n* Developers should not use the `--insecure` or the `--insecure-skip-secure-default-rule-enforcement` flags and configure their default rule to implement \"deny by default\".\n* Reject HTTP paths containing encoded slashes in the layers in front of heimdall. Some proxies, like e.g., Traefik, do that by default.\n* Include the ID of the rule expected to be executed in the JWT issued by heimdall and verify that value in the 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-43jv-5j4x-qv67"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42272"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/pull/3207"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/commit/8b0de6aba23a047cfee3081df878271bb17f4351"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/dadrus/heimdall"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/releases/tag/v0.17.14"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-178", "CWE-436" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-25T23:29:40Z",
    "nvd_published_at" : "2026-05-08T04:16:22Z"
  }
}