CVE-2025-29927

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2025-03-21. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2025-7243 (ENISA EUVD) · GHSA-f82v-jwr5-mffw (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 99%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 99%CVSS: 9.1Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
96
EG Risk 96/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation99% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
99%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
99% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 21, 2025

Last Modified

September 10, 2025

Advisory Details (8)

Auto-updated Aug 1, 2026
Patch available. Sources: github_release, github, github_commit.
Web page

NetApp Product Security

https://security.netapp.com/advisory/ntap-20250328-0002/
Web page

oss-security - Re: CVE-2025-29927: Authorization Bypass in Next.js Middleware

http://www.openwall.com/lists/oss-security/2025/03/23/4
Web page

oss-security - CVE-2025-29927: Authorization Bypass in Next.js Middleware

http://www.openwall.com/lists/oss-security/2025/03/23/3
GitHub advisoryMentions a patch (unverified)

Authorization Bypass in Next.js Middleware · Advisory · vercel/next.js · GitHub

Affected: 13.5.9

https://github.com/vercel/next.js/security/advisories/GHSA-f82v-jwr5-mffw
GitHub release Patch Available

v13.5.9

Patch available: vercel/next.js v13.5.9

https://github.com/vercel/next.js/releases/tag/v13.5.9
GitHub release Patch Available

v12.3.5

Patch available: vercel/next.js v12.3.5

https://github.com/vercel/next.js/releases/tag/v12.3.5
GitHub commit

commit 5fd3ae8f8542 (vercel/next.js)

Fix landed in vercel/next.js commit 5fd3ae8f8542 — awaiting tagged release

https://github.com/vercel/next.js/commit/5fd3ae8f8542677c6294f32d18022731eab6fe48
GitHub commit

commit 52a078da3884 (vercel/next.js)

Fix landed in vercel/next.js commit 52a078da3884 — awaiting tagged release

https://github.com/vercel/next.js/commit/52a078da3884efe6501613c7834a3d02a91676d2

Vendor Advisories for CVE-2025-29927(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmnext @ 13.5.9 (fixes >= 13.0.0, < 13.5.9)—ghsa
npmnext @ 14.2.25 (fixes >= 14.0.0, < 14.2.25)—ghsa
npmnext @ 15.2.3 (fixes >= 15.0.0, < 15.2.3)—ghsa
npmnext @ 12.3.5 (fixes >= 12.0.0, < 12.3.5)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
next—
  • 13.0.0 up to 13.5.9: fixed in 13.5.9
  • 14.0.0 up to 14.2.25: fixed in 14.2.25
  • 15.0.0 up to 15.2.3: fixed in 15.2.3
  • 12.0.0 up to 12.3.5: fixed in 12.3.5
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 104 rows on record for this CVE, as 91 entries (9 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 4 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 18:15 UTCEchelonGraph re-scored
  2. 2026-11-12 18:15 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-11 18:09 UTCEchelonGraph re-scored
  4. 2026-11-11 18:09 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-11-11 16:36 UTCEPSS rescoreEPSS 99% · 99th percentile
  6. 2026-11-10 18:00 UTCEchelonGraph re-scored
  7. 2026-11-10 18:00 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-11-09 17:54 UTCEchelonGraph re-scored
  9. 2026-11-09 17:54 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-11-08 17:48 UTCEchelonGraph re-scored
  11. 2026-11-08 17:48 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-11-07 17:42 UTCEchelonGraph re-scored
  13. 2026-11-07 17:42 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-11-06 17:36 UTCEchelonGraph re-scored
  15. 2026-11-06 17:36 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-11-05 17:30 UTCEchelonGraph re-scored
  17. 2026-11-05 17:30 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-11-05 11:25 UTCOSV refresh
  19. 2026-11-04 17:21 UTCEchelonGraph re-scored
  20. 2026-11-04 17:21 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-11-04 16:33 UTCEPSS rescoreEPSS 99% · 99th percentile
  22. 2026-11-03 17:14 UTCEchelonGraph re-scored
  23. 2026-11-03 17:14 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-11-02 17:08 UTCEchelonGraph re-scored
  25. 2026-11-02 17:08 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
Show 66 more
  1. 2026-11-01 17:02 UTCEchelonGraph re-scored
  2. 2026-11-01 17:01 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-01 08:07 UTCGHSA enrichmentGHSA-f82v-jwr5-mffw · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-01 08:07 UTCEchelonGraph re-scored
  5. 2026-10-31 16:56 UTCEchelonGraph re-scored
  6. 2026-10-30 16:36 UTCEchelonGraph re-scored
  7. 2026-10-28 20:34 UTCEchelonGraph re-scored
  8. 2026-10-27 20:29 UTCEchelonGraph re-scored
  9. 2026-10-26 20:23 UTCEchelonGraph re-scored
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 99% · 99th percentile
  11. 2026-10-25 16:37 UTCEchelonGraph re-scored
  12. 2026-10-25 16:31 UTCEPSS rescoreEPSS 99% · 99th percentile
  13. 2026-10-24 18:20 UTCEchelonGraph re-scored
  14. 2026-10-23 18:14 UTCEchelonGraph re-scored
  15. 2026-10-22 17:58 UTCEchelonGraph re-scored
  16. 2026-10-21 17:23 UTCEchelonGraph re-scored
  17. 2026-10-20 16:59 UTCEchelonGraph re-scored
  18. 2026-10-19 16:51 UTCEchelonGraph re-scored
  19. 2026-10-18 16:41 UTCEchelonGraph re-scored
  20. 2026-10-18 05:40 UTCEchelonGraph re-scored
  21. 2026-10-17 22:08 UTCEchelonGraph re-scored
  22. 2026-10-17 16:32 UTCEPSS rescoreEPSS 99% · 99th percentile
  23. 2026-10-16 22:00 UTCEchelonGraph re-scored
  24. 2026-10-15 18:22 UTCEchelonGraph re-scored
  25. 2026-10-14 12:07 UTCEchelonGraph re-scored
  26. 2026-10-12 17:13 UTCEchelonGraph re-scored
  27. 2026-10-11 20:45 UTCEchelonGraph re-scored
  28. 2026-10-11 18:55 UTCEchelonGraph re-scored
  29. 2026-10-11 15:33 UTCEchelonGraph re-scored
  30. 2026-10-06 15:16 UTCEPSS rescoreEPSS 99% · 99th percentile
  31. 2026-10-05 17:42 UTCEPSS rescoreEPSS 99% · 99th percentile
  32. 2026-10-02 19:40 UTCOSV refresh
  33. 2026-09-30 15:02 UTCEPSS rescoreEPSS 99% · 99th percentile
  34. 2026-09-16 14:07 UTCEPSS rescoreEPSS 99% · 99th percentile
  35. 2026-09-13 17:09 UTCOSV refresh
  36. 2026-09-07 16:00 UTCEPSS rescoreEPSS 99% · 99th percentile
  37. 2026-09-06 13:46 UTCEPSS rescoreEPSS 99% · 99th percentile
  38. 2026-08-30 19:16 UTCEPSS rescoreEPSS 99% · 99th percentile
  39. 2026-08-28 21:40 UTCEPSS rescoreEPSS 99% · 99th percentile
  40. 2026-08-25 18:39 UTCOSV refresh
  41. 2026-08-24 14:16 UTCEPSS rescoreEPSS 99% · 99th percentile
  42. 2026-08-17 13:46 UTCEPSS rescoreEPSS 99% · 99th percentile
  43. 2026-08-13 21:59 UTCEPSS rescoreEPSS 99% · 99th percentile
  44. 2026-08-09 10:44 UTCOSV refresh
  45. 2026-08-06 13:46 UTCEPSS rescoreEPSS 99% · 99th percentile
  46. 2026-08-05 19:16 UTCEPSS rescoreEPSS 99% · 99th percentile
  47. 2026-08-04 10:37 UTCEPSS rescoreEPSS 99% · 99th percentile
  48. 2026-07-30 16:27 UTCEPSS rescoreEPSS 99% · 99th percentile
  49. 2026-07-30 01:29 UTCEPSS rescoreEPSS 99% · 99th percentile
  50. 2026-07-27 14:12 UTCEPSS rescoreEPSS 99% · 99th percentile
  51. 2026-07-24 11:41 UTCOSV refresh
  52. 2026-07-23 02:52 UTCEchelonGraph re-scored
  53. 2026-07-15 16:57 UTCEPSS rescoreEPSS 99% · 99th percentile
  54. 2026-07-09 19:09 UTCEPSS rescoreEPSS 99% · 99th percentile
  55. 2026-07-07 06:51 UTCOSV refresh
  56. 2026-06-24 14:04 UTCEPSS rescoreEPSS 99.6% · 99th percentile
  57. 2026-06-22 14:25 UTCEPSS rescoreEPSS 98% · 99th percentile
  58. 2026-06-18 18:05 UTCOSV refresh
  59. 2026-06-17 17:52 UTCEPSS rescoreEPSS 93% · 99th percentile
  60. 2026-06-15 17:48 UTCEPSS rescoreEPSS 93% · 99th percentile
  61. 2026-06-12 23:11 UTCEPSS rescoreEPSS 92% · 99th percentile
  62. 2026-06-10 22:18 UTCEPSS rescoreEPSS 92% · 99th percentile
  63. 2026-06-08 14:16 UTCEPSS rescoreEPSS 92% · 99th percentile
  64. 2026-06-07 15:24 UTCEPSS rescoreEPSS 92% · 99th percentile
  65. 2026-06-06 13:47 UTCEPSS rescoreEPSS 92% · 99th percentile
  66. 2026-06-05 06:10 UTCEPSS rescoreEPSS 92% · 99th percentile

Publicly available exploits

(14 references, 10 shown)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 9 GitHub PoCs), as are 1 Nuclei detection template, 2 GitHub checker repositories. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitauxiliary/scanner/http/nextjs_middleware_auth_bypass✓ verified
    Published Jun 23, 2026

    Next.js Middleware Authorization Bypass Scanner

    Open source ↗
  • GitHub PoCUNICORDev/exploit-CVE-2025-29927
    Published Apr 14, 2025

    Exploit for CVE-2025-29927 (Next.js) - Authorization Bypass

    Open source ↗
  • GitHub PoCgotr00t0day/CVE-2025-29927
    Published Apr 6, 2025

    Next.js Middleware Bypass Scanne

    Open source ↗
  • Exploit-DBEDB-52124
    Published Apr 5, 2025

    Next.js Middleware 15.2.2 - Authorization Bypass

    Open source ↗
  • GitHub PoCAnonKryptiQuz/NextSploit
    Published Mar 28, 2025

    NextSploit is a command-line tool designed to detect and exploit CVE-2025-29927, a security flaw in Next.js

    Open source ↗
  • GitHub PoCkOaDT/poc-cve-2025-29927
    Published Mar 26, 2025

    This repository contains a proof of concept (POC) and an exploit script for CVE-2025-29927, a critical vulnerability in Next.js that allows attackers to bypass authorization checks implemented in middleware.

    Open source ↗
  • GitHub checkerphoscoder/ghost-route
    Published Mar 25, 2025

    Ghost Route detects if a Next JS site is vulnerable to the corrupt middleware bypass bug (CVE-2025-29927)

    Open source ↗
  • GitHub checker6mile/nextjs-CVE-2025-29927
    Published Mar 23, 2025

    A Nuclei template to detect CVE-2025-29927 the Next.js authentication bypass vulnerability

    Open source ↗
  • GitHub PoCaydinnyunus/CVE-2025-29927
    Published Mar 23, 2025

    CVE-2025-29927 Proof of Concept

    Open source ↗
  • GitHub PoCazu/nextjs-cve-2025-29927-poc
    Published Mar 23, 2025

    Next.js PoC for CVE-2025-29927

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-29927?
CVE-2025-29927 is a critical-severity vulnerability; its CVE record was published on March 21, 2025. Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a…
When was the CVE record for CVE-2025-29927 published?
The CVE record for CVE-2025-29927 was published on March 21, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 10, 2025; the record at its source may have been updated since.
Is CVE-2025-29927 actively exploited?
CVE-2025-29927 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 99% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-29927?
CVE-2025-29927 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-29927?
A fix for CVE-2025-29927 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-29927 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-29927

Explore →

Is Your Infrastructure Affected by CVE-2025-29927?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs