CVE-2026-42274: Heimdall has an authorization bypass via path normalization mismatch
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. 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.
Published Apr 25, 2026 · Updated May 12, 2026
Affected packages
github.com/dadrus/heimdall
- Ecosystem
- Go
- Affected
- < 0.17.14
- Fixed in
- 0.17.14
- Check
go list -m github.com/dadrus/heimdall
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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. 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.
id: rule-1
match:
routes:
- path: /user/**
execute: # configured to require authentication and authorization
# ...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`).
- 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.
References
- https://github.com/dadrus/heimdall/security/advisories/GHSA-3q34-rx83-r6mq
- 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
- https://www.rfc-editor.org/rfc/rfc3986#section-6.2.2.3
- https://nvd.nist.gov/vuln/detail/CVE-2026-42274
- https://github.com/dadrus/heimdall/pull/3209
- https://github.com/dadrus/heimdall/commit/b5dfa484b7a8c2ce6d8691c026f9da867719947a
- https://github.com/dadrus/heimdall/releases/tag/v0.17.14
- https://github.com/advisories/GHSA-3q34-rx83-r6mq
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-57209
Heimdall: Forwarded Header Injection via Unsanitized Host Header in Proxy Mode
high7.0Jun 18, 2026CVE-2026-42272
Heimdall: Case-sensitive handling of URL-encoded slashes may lead to inconsistent path interpretation
high7.8Apr 25, 2026CVE-2026-42273
Heimdall: Case-sensitive host matching may lead to policy bypass
high7.8Apr 25, 2026CVE-2026-32811
Heimdall: Path received via Envoy gRPC corrupted when containing query string
high8.2Mar 18, 2026
