p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in @opennextjs/cloudflare

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für @opennextjs/cloudflare: 1. Davon im KEV-Katalog: 0.

RSS ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 2

  1. CVE-2026-100409

    Hoch · CVSS 7.5EPSS 0,3%Korrektur verfügbar

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

    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 no

    • Auf 1.20.2 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2025-6087

    Hoch · CVSS 7.8EPSS 0,97%Korrektur verfügbar

    SSRF vulnerability in opennextjs-cloudflare via /_next/image endpoint

    A Server-Side Request Forgery (SSRF) vulnerability was identified in the @opennextjs/cloudflare package. The vulnerability stems from an unimplemented feature in the Cloudflare adapter for Open Next, which allowed unauthenticated users to proxy arbitrary remote content via the /_next/image endpoint. This issue allowed attackers to load remote resources from arbitrary hosts under the victim site’s domain for any site deployed using the Cloudflare adapter for Open Next.  For example: https://victim-site.com/_next/image?url=https://attacker.com In this example, attacker-controlled content from attacker.com is served through the victim s

    • Auf 1.17.1 aktualisieren
    • Auf 1.3.0 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →