# CVE-2026-72582: fastschema - Unauthenticated NULL Pointer Dereference DoS in Account Recovery Endpoint

> Unauthenticated attackers can crash the fastschema server via a null pointer dereference in the account recovery endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-x3w9-j9j5-qcw7

## What is CVE-2026-72582?

CVE-2026-72582 is a high-severity vulnerability in fastschema, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A NULL pointer dereference vulnerability in fastschema through v0.15.1 allows an unauthenticated remote attacker to crash the server process with a single HTTP request. The sendOTPEmail function in pkg/auth/local.go dereferences a pointer obtained from an unchecked error path without validating it is non-nil, causing a fatal panic that terminates the entire server when a recovery request is sent to the /api/auth/local/recover endpoint.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-72582?


## How do I fix CVE-2026-72582?

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

## Is CVE-2026-72582 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72582 and fix it if it is affected.

What it is: CVE-2026-72582 is a high-severity vulnerability in fastschema, published on 10 Aug 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-2026-72582 in the wild and no public exploit code.

Affected product: fastschema. 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-2026-72582/ (Markdown: https://insights.sbomify.com/CVE-2026-72582/index.md)
```

## Sources

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

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