https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 12:54:15 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-277789 EUVD-2026-277789 https://cve.radiocsirt.org/vuln/euvd-2026-277789 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33494 <p>ORY Oathkeeper is an Identity &amp; Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. Versions prior to 26.2.0 are vulnerable to an authorization bypass via HTTP path traversal. An attacker can craft a URL containing path traversal sequences (e.g. `/public/../admin/secrets`) that resolves to a protected path after normalization, but is matched against a permissive rule because the raw, un-normalized path is used during rule evaluation. Version 26.2.0 contains a patch.</p> <p>ORY Oathkeeper is an Identity &amp; Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. Versions prior to 26.2.0 are vulnerable to an authorization bypass via HTTP path traversal. An attacker can craft a URL containing path traversal sequences (e.g. `/public/../admin/secrets`) that resolves to a protected path after normalization, but is matched against a permissive rule because the raw, un-normalized path is used during rule evaluation. Version 26.2.0 contains a patch.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-33494 https://cve.radiocsirt.org/vuln/ghsa-p224-6x5r-fjpm <p><strong>Affected:</strong> Go: github.com/ory/oathkeeper</p> <p>## Description</p> <p>Ory Oathkeeper is vulnerable to an authorization bypass via HTTP path traversal. An attacker can craft a URL containing path traversal sequences (e.g. `/public/../admin/secrets`) that resolves to a protected path after normalization, but is matched against a permissive rule because the raw, un-normalized path is used during rule evaluation.</p> <p>## Preconditions</p> <p>Ory Oathkeeper rules are typically configured with patterns like:</p> <p>``` /public/&lt;.*&gt; → allow unauthenticated access /admin/&lt;.*&gt; → require authentication ```</p> <p>Without path normalization, a request to `/public/../admin/secrets` is matched against the raw path `/public/../admin/secrets`. This matches the `/public/&lt;.*&gt;` rule, bypassing the authentication required for `/admin/secrets`. After Ory Oathkeeper permits the request, the upstream server normalizes the path and serves the protected `/admin/secrets` resource.</p> <p>## Mitigation</p> <p>Going forward, Ory Oathkeeper normalizes the request path before performing rule matching and before forwarding. The path `/public/../admin/secrets` is normalized to `/admin/secrets`, which correctly matches the `/admin/&lt;.*&gt;` rule and triggers authentication.</p> <p>As an immediate mitigation, all requests reaching Oathkeeper should be normalized, as described in the section below. Oathkeeper should be upgraded to a fixed version as soon as possible.</p> <p>## Defense in depth: Cleaning paths before Oathkeeper</p> <p>Even after this fix, it is good practice to normalize HTTP paths in the layers…</p> <p><strong>Affected:</strong> Go: github.com/ory/oathkeeper</p> <p>## Description</p> <p>Ory Oathkeeper is vulnerable to an authorization bypass via HTTP path traversal. An attacker can craft a URL containing path traversal sequences (e.g. `/public/../admin/secrets`) that resolves to a protected path after normalization, but is matched against a permissive rule because the raw, un-normalized path is used during rule evaluation.</p> <p>## Preconditions</p> <p>Ory Oathkeeper rules are typically configured with patterns like:</p> <p>``` /public/&lt;.*&gt; → allow unauthenticated access /admin/&lt;.*&gt; → require authentication ```</p> <p>Without path normalization, a request to `/public/../admin/secrets` is matched against the raw path `/public/../admin/secrets`. This matches the `/public/&lt;.*&gt;` rule, bypassing the authentication required for `/admin/secrets`. After Ory Oathkeeper permits the request, the upstream server normalizes the path and serves the protected `/admin/secrets` resource.</p> <p>## Mitigation</p> <p>Going forward, Ory Oathkeeper normalizes the request path before performing rule matching and before forwarding. The path `/public/../admin/secrets` is normalized to `/admin/secrets`, which correctly matches the `/admin/&lt;.*&gt;` rule and triggers authentication.</p> <p>As an immediate mitigation, all requests reaching Oathkeeper should be normalized, as described in the section below. Oathkeeper should be upgraded to a fixed version as soon as possible.</p> <p>## Defense in depth: Cleaning paths before Oathkeeper</p> <p>Even after this fix, it is good practice to normalize HTTP paths in the layers…</p> https://cve.radiocsirt.org/vuln/ghsa-p224-6x5r-fjpm