github.com/dadrus/heimdall
Affected
- introduced
0, fixed0.17.14(semver)
Fixed versions
0.17.14
Fix
- Fixed version
0.17.14go get github.com/dadrus/[email protected]
Advisory
Also known as: CVE-2026-42274, GO-2026-5097
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. 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:
Workarounds
High Basis: The source's own band: HIGH
0, fixed 0.17.14 (semver)0.17.14
0.17.14go get github.com/dadrus/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0