<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-16T09:55:20.510788+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-100409</id>
    <title>fkie_cve-2026-100409</title>
    <updated>2026-10-16T09:55:20.529773+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenNext Cloudflare is an open Next.js adapter for Cloudflare. From 0.3.0 until 1.20.2, applications that enable enableCacheInterception, rely on middleware for access control, and have a matching cached protected route process encoded pathnames inconsistently between middleware matching and cache lookup. An unauthenticated attacker can use a percent-encoded pathname that does not match authorization middleware but decodes to the cache key of a protected route, causing cached content to be returned without authorization. Malformed encodings can also be partially decoded, allowing cache lookup to continue with a pathname that middleware did not evaluate consistently. This issue is fixed in version 1.20.2.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-100409"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-2vc4-c4r6-p6v6</id>
    <title>GHSA-2vc4-c4r6-p6v6 — OpenNext Cloudflare: Cache interception can bypass middleware protection for encoded paths</title>
    <updated>2026-10-16T09:55:20.529880+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @opennextjs/cloudflare</p>
<p>## Summary</p>
<p>When cache interception is enabled, `@opennextjs/cloudflare` can interpret percent-encoded paths differently during middleware matching and cache lookup.</p>
<p>An encoded request may fail to match authorization middleware, then be decoded into the cache key of a protected route. The cached response may consequently be returned without invoking the middleware.</p>
<p>`enableCacheInterception` is disabled by default.</p>
<p>## Impact</p>
<p>A remote unauthenticated attacker may retrieve cached content from routes intended to be protected by middleware.</p>
<p>An application is affected when it:</p>
<p>- explicitly enables `enableCacheInterception`;
- relies on middleware for access control; and
- has a matching cached route.</p>
<p>## Details</p>
<p>Middleware matching previously used the encoded request pathname, while cache interception decoded the pathname before selecting a cache entry.</p>
<p>For example, consider an application with:</p>
<p>- middleware matcher `/admin/:path*`;
- middleware returning `401 Authentication required` for `/admin`;
- a statically generated, cached `/admin` route; and
- cache interception enabled:</p>
<p>```ts
export default defineCloudflareConfig({
  incrementalCache: staticAssetsIncrementalCache,
  enableCacheInterception: true,
});
```</p>
<p>An attacker can request:</p>
<p>```http
GET /%61dmin
```</p>
<p>The encoded pathname does not match `/admin/:path*`, so the authorization middleware is not invoked. Cache interception then decodes `%61dmin` to `admin` and may return the cached `/admin` response:</p>
<p>```http…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-2vc4-c4r6-p6v6"/>
  </entry>
</feed>
