# CVE-2026-92002: MISP: Authentication failure logging suppressed during Redis unavailability

> Attackers can hide brute-force attempts from logs when Redis is down, preventing detection of authentication failures in MISP.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-f6c4-mg5x-232x

## What is CVE-2026-92002?

CVE-2026-92002 is a medium-severity vulnerability in MISP, published on 15 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Affected versions of MISP use Redis to throttle repeated authentication-failure log entries. The intent is to avoid excessive duplicate logs while still recording failed authentication activity.

However, User->setupRedis() returns false when Redis cannot be reached. The vulnerable _shouldLog() logic only returned true when a Redis instance existed and no throttle key was present. Therefore, when Redis was unavailable, the function did not allow the log write at all, effectively silencing authentication-failure logging for the duration of the outage.

Version affected: ≤2.5.45

Weakness: CWE-778 (Insufficient Logging)

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


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

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

## Is CVE-2026-92002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92002 is a medium-severity vulnerability in MISP, published on 15 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92002 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-92002/ (Markdown: https://insights.sbomify.com/CVE-2026-92002/index.md)
```

## Sources

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

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