<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T05:16:05.548254+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-310027</id>
    <title>EUVD-2026-310027</title>
    <updated>2026-10-06T05:16:05.595559+00:00</updated>
    <content>EUVD-2026-310027</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-310027"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42274</id>
    <title>fkie_cve-2026-42274</title>
    <updated>2026-10-06T05:16:05.595604+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-42274"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3q34-rx83-r6mq</id>
    <title>GHSA-3q34-rx83-r6mq — Heimdall has an authorization bypass via path normalization mismatch</title>
    <updated>2026-10-06T05:16:05.595642+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/dadrus/heimdall</p>
<p>### Summary</p>
<p>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`).</p>
<p>### Details</p>
<p>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.</p>
<p>```yaml
id: rule-1
match:
  routes:
    - path: /user/**
execute: # configured to require authentication and authorization
  # ...
```</p>
<p>```yaml
id: rule-2
match:
  routes:
    - path: /public/**
execute: # configured to allow anonymous access
  # ...
```</p>
<p>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`.</p>
<p>### Impact</p>
<p>Bypass of access control policies enforced by heimdall may lead to the following consequences:</p>
<p>* Access to or modification of data that should be restricted
* Invocation of functionality that is expected to require authenti…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3q34-rx83-r6mq"/>
  </entry>
</feed>
