Resource exhaustion via unthrottled authentication log writes
Published Sep 15, 2026 · Updated Sep 15, 2026
Improper throttling in MISP 2.5.45 and earlier allows remote attackers to exhaust storage through failed API authentication requests. The missing-key and wrong-length-key branches write auth_fail records directly through the Log model instead of consulting _shouldLog(). No authentication is required; a request flood can create an unbounded stream of durable database log entries and interrupt service.
Summary
What happened
Improper throttling in MISP 2.5.45 and earlier allows remote attackers to exhaust storage through failed API authentication requests. The missing-key and wrong-length-key branches write auth_fail records directly through the Log model instead of consulting _shouldLog(). No authentication is required; a request flood can create an unbounded stream of durable database log entries and interrupt service.
The record
- CVE
- CVE-2026-92003
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- MISP Project
- Product
- MISP
- Classifications
- T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.5.46
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo