# CVE-2026-92003: MISP Unthrottled Authentication Failure Log Writes Enable Resource Exhaustion

> Attackers can exhaust resources by triggering unthrottled authentication failure logs in MISP, leading to denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-rr6q-fmv4-p23m

## What is CVE-2026-92003?

CVE-2026-92003 is a medium-severity denial of service vulnerability in MISP, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions of MISP do not consistently apply the existing authentication-failure logging throttle.

Two API authentication failure branches wrote directly to the Log model:

 - API requests with no authentication key;
 - requests supplying an API key with an incorrect length

Unlike other authentication failures, these paths bypassed _shouldLog(), so every request could create another durable auth_fail entry.

Version affected: ≤2.5.45

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-92003 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92003 is a medium-severity denial of service vulnerability in MISP, published on 15 Sep 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-92003 in the wild and no public exploit code.

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

## Sources

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

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