CVE-2024-51479
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNext.js is a React framework for building full-stack web applications. In affected versions if a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application's root directory. For example: * [Not affected] `https://example.com/` * [Affected] `https://example.com/foo` * [Not affected] `https://example.com/foo/bar`. This issue is patched in Next.js `14.2.15` and later. If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version. There are no official workarounds for this vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNext.js middleware authorization based on pathname can be bypassed for single-level paths directly under root (e.g., /foo) while root (/) and nested paths (/foo/bar) remain protected. This allows unauthorized access to affected routes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 9.5.5, < 14.2.15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Next.js versionCheck package.json for the installed next package version, or run 'npm list next' to see the installed versionAffected if Version is >= 9.5.5 and < 14.2.15
-
Confirm middleware existsLocate the middleware file: check for 'middleware.ts', 'middleware.js', or 'middleware.tsx' in the project root or src directoryAffected if Middleware file exists and is being used for route protection
-
Check for protected single-level pathsReview middleware code to identify which paths are being protected. Look for matchers or conditional logic that checks pathnamesAffected if Middleware logic protects routes using pathname-based authorization rules and includes single-level paths like /foo, /bar, etc.
-
Verify authorization logicExamine the middleware authorization implementation to determine if it relies on pathname matching to deny/allow accessAffected if Authorization decisions are based on pathname matching and the middleware does not have additional server-side validation beyond pathname checks
You are affected if your Next.js version is between 9.5.5 and 14.2.15 (exclusive) AND you use middleware to protect single-level paths directly under root (like /foo) based on pathname matching.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped14.2.15
Upgrade to Next.js 14.2.15 or later; Vercel-hosted applications are automatically protected.
Next.js 14.2.15
- Update the Next.js version in package.json to 14.2.15 or later (e.g., "next": "^14.2.15")
- Run `npm install` or `yarn install` to install the updated version
- Verify the middleware authorization logic functions correctly for pages directly under the root directory (e.g., /foo)
- Test that authorization is properly enforced and not bypassed for affected URL patterns
- If hosted on Vercel, no additional action is required as the vulnerability is automatically mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51479 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-51479 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data