CVE-2024-51479
HIGHEPSS 89th pctlDescription
Next.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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Elevated risk: more likely to be exploited than 89% of all known CVEs.
References
Related Vulnerabilities
Other CWE-285 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-29927 | Critical | 9.1 | 99% | - | Fix |
| CVE-2023-32707 | High | 8.8 | 79% | - | Fix |
| CVE-2021-28799 | Critical | 10.0 | 78% | KEV + Ransom | Fix |
| CVE-2023-48241 | High | 7.5 | 73% | - | Fix |
| CVE-2023-22480 | High | 7.3 | 67% | - | Fix |
| CVE-2022-3229 | Critical | 9.8 | 66% | - | - |
Common questions
How do I fix CVE-2024-51479?
Published advisories record a fix for 2 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2024-51479 being actively exploited?
Not that we know of. CVE-2024-51479 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 4.0% is the estimated probability that it will be exploited in the next 30 days. That is higher than 89% of all scored CVEs.
How severe is CVE-2024-51479?
CVE-2024-51479 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2024-51479 affect?
Published advisories record a fix for registry.redhat.io/rhtas/rekor-search (Red Hat / RHEL), registry.redhat.io/rhtas/rekor-search (Rocky). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2024-51479
Markdown
[](https://tridentstack.com/cve/CVE-2024-51479)HTML
<a href="https://tridentstack.com/cve/CVE-2024-51479"><img src="https://tridentstack.com/cve/badge/CVE-2024-51479.svg" alt="CVE-2024-51479"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-09-10.