Skip to main content
VulnerabilityPublished Updated

CVE-2026-42274: dadrus heimdall · Path Traversal: '.../...//

Affects dadrus heimdallSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High : upgrade to 0.17.14 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.17.14
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade heimdall and dadrus/heimdall to 0.17.14.

Affected software

ProductAffectedFixed in
dadrusheimdallAffected
  • <0.17.14
Fixed in
  • 0.17.14
GitHubdadrus/heimdallpkg:github/dadrus/heimdallOther threatsAffected
  • <0.17.14
Fixed in
  • 0.17.14

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade heimdall to version 0.17.14 or later, where this path traversal vulnerability has been patched. No other mitigation is indicated or required according to the available data.

Description

Heimdall is a cloud native Identity Aware Proxy and Access Control Decision service. Prior to version 0.17.14, 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). This issue has been patched in version 0.17.14.

References

Community reviews

Loading reviews…