By Null Ventures MCP platform
Menu

vulnerability / NVI-00011867 / Revision 3

OpenNext Cloudflare: Cache interception can bypass middleware protection for encoded paths

GitHub lists this reviewed advisory for @opennextjs/cloudflare. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.

source listedactiveGHSA-2vc4-c4r6-p6v6CVE-2026-100409

This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.

01 / Meaning

Why it matters

Published affected context helps an owner decide what evidence to gather. This report has not examined your application.

CVSS

7.5 high

GitHub source severity; exploitability and local consequence require separate evidence.

As of · GitHub Advisory Database

EPSS

0.400%

FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.34306. Missing scores are unknown.

As of · FIRST EPSS

02 / Applicability

The affected context

Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.

@opennextjs/cloudflare

source listed
  • >= 0.3.0, < 1.20.2

## Summary When cache interception is enabled, `@opennextjs/cloudflare` can interpret percent-encoded paths differently during middleware matching and cache lookup. 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. `enableCacheInterception` is disabled by default. ## Impact A remote unauthenticated attacker may retrieve cached content from routes intended to be protected by middleware. An application is affected when it: - explicitly enables `enableCacheInterception`; - relies on middleware for access control; and - has a matching cached route. ## Details Middleware matching previously used the encoded request pathname, while cache interception decoded the pathname before selecting a cache entry. For example, consider an application with: - middleware matcher `/admin/:path*`; - middleware returning `401 Authentication required` for `/admin`; - a statically generated, cached `/admin` route; and - cache interception enabled: ```ts export default defineCloudflareConfig({ incrementalCache: staticAssetsIncrementalCache, e

GitHub Advisory Database

03 / Response

What to do next

  1. investigate

    Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS

A fixed release is not deployment evidence.

Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.

04 / Limits

What this report cannot establish

  • Customer inventory, deployment, reachability and exploitation have not been inspected.
  • NVD lastModified does not establish freshness of every associated CPE record.
Read the collection and interpretation limits ↗

05 / Provenance

Sources you can inspect

Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.

  1. GHSA-2vc4-c4r6-p6v6 ↗

    GitHub Advisory Database · vendor advisory

    Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.

  2. CVE-2026-100409 ↗

    NIST National Vulnerability Database · official catalog

    Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.

  3. CVE-2026-100409 ↗

    FIRST EPSS · official catalog

    Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.

Public revision history

Only published revisions appear here. Routine fetches do not create a material-change event.

  1. Revision 3 ·

    Source facts changed; compare the preserved prior revision.

  2. Revision 2 ·

    Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.

  3. Revision 1 ·

    First indexed by Null; source disclosure date is shown separately.

Read the public revision data ↗

The next step is private

Bring the question into your environment.

The connected workflow is a development preview for inventory, contextual matching, owner decisions and evidence-based verification. No system-specific result is generated by this page.

See the synthetic workflow preview ↗