c.im is one of the many independent Mastodon servers you can use to participate in the fediverse.
C.IM is a general, mainly English-speaking Mastodon instance.

Server stats:

2.8K
active users

#Nextjs

17 posts16 participants5 posts today

Critical Next.js Middleware Vulnerability (CVE-2025-29927)

A major auth bypass vulnerability in Next.js middleware (prior to v14.2.25 / v15.2.3) allows attackers to inject the x-middleware-subrequest header and bypass authorization entirely. Exploitable via simple HTTP requests—no user interaction, no special permissions.

Patch. Now. Or block the header manually.

GitHub scored this 9.1 CRITICAL, but the real issue? This flaw exposes a systemic weakness in middleware validation, and some vendors weren’t exactly upfront about the risks.

Details + POC: zeropath.com/blog/nextjs-middl
NVD: nvd.nist.gov/vuln/detail/CVE-2

Security theater is easy. Secure defaults and transparency are harder—but essential.

zeropath.comNext.js Middleware Exploit: Deep Dive into CVE-2025-29927 Authorization Bypass - ZeroPath BlogExplore the critical CVE-2025-29927 vulnerability in Next.js middleware, enabling attackers to bypass authorization checks and gain unauthorized access.

⚠️ Une faille critique dans Next.js permet de contourner les vérifications d'autorisation effectuées dans le middleware.

👉 Framework React trés populaire pour le rendu web côté serveur.

🔍 Détails techniques

En injectant l'en-tête x-middleware-subrequest, un attaquant peut bypasser les contrôles d'accès et accéder à des ressources normalement protégées.

💥 Exploit documenté ici
⬇️
"Next.js and the corrupt middleware: the authorizing artifact"
👇
zhero-web-sec.github.io/resear

🛡️ Versions vulnérables

  • 15.x < 15.2.3
  • 14.x < 14.2.25
  • 11.1.4 → 13.5.6

🔧 Solutions

✔️ Mettez à jour vers 15.2.3 ou 14.2.25

👇
nextjs.org/blog/cve-2025-29927
⬇️
github.com/advisories/GHSA-f82

✔️ En attendant : bloquez les requêtes contenant x-middleware-subrequest côté serveur / WAF

🛰️ Et effectivement selon le moteur de recherche de surface d’attaque ONYPHE,

il y en a un paquet… y compris en Suisse 🇨🇭

zhero_web_security · Next.js and the corrupt middleware: the authorizing artifactCVE-2025-29927

Готовим геотаргетинг на nginx + GeoIP2 и связываем с локализацией в Next.js

В этой статье поделюсь быстрым способом настройки геотаргетинга на nginx + GeoIP2 в связке с локализацией Next.js на примере решения реальной задачи. Вы узнаете как подключить и настроить GeoIP2 к nginx , как приоритизировать и настроить критерии выбора домена и локали, и как подружить это с Next.js

habr.com/ru/articles/893294/

ХабрГотовим геотаргетинг на nginx + GeoIP2 и связываем с локализацией в Next.jsМеня зовут Александр Леуцкий, и я давно разрабатываю фронтенд, хотя нередко занимаюсь и другими задачами. В этой статье поделюсь быстрым способом настройки геотаргетинга на nginx + GeoIP2 в связке с...

Question from a noob with no clue about this stuff:

Is next.js v14 still maintained? From what I can tell there are only two release channels with next.js: Stable and Canary. Right now those correspond to 15.2.x and 15.3.x respectively.

Where does that leave v14 and older versions of next.js in terms of support and patching?