# CVE-2020-36950: Laravel Nova 3.7.0 - 'range' DoS

> Authenticated users can crash the Laravel Nova application by sending simultaneous requests with an extremely high range parameter value.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-xwgc-2jgm-rr7j

## What is CVE-2020-36950?

CVE-2020-36950 is a high-severity denial of service vulnerability in Laravel Nova, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Laravel Nova 3.7.0 contains a denial of service vulnerability that allows authenticated users to crash the application by manipulating the 'range' parameter. Attackers can send simultaneous requests with an extremely high range value to overwhelm and crash the server.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2020-36950?


## How do I fix CVE-2020-36950?

No fix has been published for CVE-2020-36950 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36950 being exploited?

There is no known exploitation of CVE-2020-36950 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36950 and fix it if it is affected.

What it is: CVE-2020-36950 is a high-severity denial of service vulnerability in Laravel Nova, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36950 in the wild and no public exploit code.

Affected product: Laravel Nova. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36950/ (Markdown: https://insights.sbomify.com/CVE-2020-36950/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36950
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36950
- OSV: https://osv.dev/vulnerability/CVE-2020-36950

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36950/
Summaries are generated and may contain mistakes; the official description above is the record.