<?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-03T10:52:41.189877+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-273769</id>
    <title>EUVD-2026-273769</title>
    <updated>2026-10-03T10:52:41.259073+00:00</updated>
    <content>EUVD-2026-273769</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-273769"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27587</id>
    <title>fkie_cve-2026-27587</title>
    <updated>2026-10-03T10:52:41.259137+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy's HTTP `path` request matcher is intended to be case-insensitive, but when the match pattern contains percent-escape sequences (`%xx`) it compares against the request's escaped path without lowercasing. An attacker can bypass path-based routing and any access controls attached to that route by changing the casing of the request path. Version 2.11.1 contains a fix for the issue.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-27587"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-g7pc-pc7g-h8jh</id>
    <title>GHSA-g7pc-pc7g-h8jh — Caddy: MatchPath %xx (escaped-path) branch skips case normalization, enabling path-based route/auth bypass</title>
    <updated>2026-10-03T10:52:41.259197+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/caddyserver/caddy/v2</p>
<p>### Summary
Caddy's HTTP `path` request matcher is intended to be case-insensitive, but when the match pattern contains percent-escape sequences (`%xx`) it compares against the request's escaped path without lowercasing. An attacker can bypass path-based routing and any access controls attached to that route by changing the casing of the request path.</p>
<p>### Details
In Caddy `v2.10.2`, `MatchPath` is explicitly designed to be case-insensitive and lowercases match patterns during provisioning:</p>
<p>- `modules/caddyhttp/matchers.go`: rationale captured in the `MatchPath` comment.
- `MatchPath.Provision` lowercases configured patterns via `strings.ToLower`.
- `MatchPath.MatchWithError` lowercases the request path for the normal matching path: `reqPath := strings.ToLower(r.URL.Path)`.</p>
<p>But when a match pattern contains a percent sign (`%`), `MatchPath.MatchWithError` switches to "escaped space" matching and builds the comparison string from `r.URL.EscapedPath()`:</p>
<p>- `reqPathForPattern := CleanPath(r.URL.EscapedPath(), mergeSlashes)`
- If it doesn't match, it `continue`s (skipping the remaining matching logic for that pattern).</p>
<p>Because `r.URL.EscapedPath()` is not lowercased, case differences in the request path can cause the escaped-space match to fail even though `MatchPath` is meant to be case-insensitive. For example, with a pattern of `/admin%2Fpanel`:</p>
<p>- Requesting `/admin%2Fpanel` matches and can be denied as intended.
- Requesting `/ADMIN%2Fpanel` does not match and falls thro…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-g7pc-pc7g-h8jh"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27587</id>
    <title>UBUNTU-CVE-2026-27587</title>
    <updated>2026-10-03T10:52:41.259327+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:24.04:LTS: caddy, Ubuntu:25.10: caddy, Ubuntu:Pro:26.04:LTS: caddy</p>
<p>Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy's HTTP `path` request matcher is intended to be case-insensitive, but when the match pattern contains percent-escape sequences (`%xx`) it compares against the request's escaped path without lowercasing. An attacker can bypass path-based routing and any access controls attached to that route by changing the casing of the request path. Version 2.11.1 contains a fix for the issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27587"/>
  </entry>
</feed>
