CVE-2024-10821
A public proof of concept exists; no exploitation attested.
- Published2025-03-20
- WeaknessCWE-835
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A Denial of Service (DoS) vulnerability in the multipart request boundary processing mechanism of the Invoke-AI server (version v5.0.1) allows unauthenticated attackers to cause excessive resource consumption. The server fails to handle excessive characters appended to the end of multipart boundaries, leading to an infinite loop and a complete denial of service for all users. The affected endpoint is `/api/v1/images/upload`.
Timeline
dates in UTC- 2025-03-2010:15CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.0 | ≤ 5.0.2 | no fix published | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As @huntr_ai, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- invoke-ai/invokeaiAffected
- ≤ latestno fix statedcustom
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-10-15
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-11-01 01:02 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2025-03-20
- PoC-in-GitHub2 repositories, unverifiedknown since 2026-11-01dannyEndorTest/invokeaidannyEndorTest/invokeai-consumer
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionpoc2025-03-20
- CNACVSS 3.07.5known since 2026-10-23
- CNAweakness (CWE)CWE-835known since 2026-10-23
- FIRST EPSSEPSS score0.6 %2026-11-17
- PoC-in-GitHubproof of concept2known since 2026-11-01
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2025-03-21
Identifiers
- EUVD-2025-7093same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-6f6x-f56q-5xgvsame flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2026-1466same flawPyPA Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2025-03-20
- Last Modified
- 2026-06-17
- NVD status
- Deferred
- GitHub Advisory
- GHSA-6f6x-f56q-5xgv
Frequently asked questions
What is CVE-2024-10821?
Is CVE-2024-10821 actively exploited?
What is the CVSS score for CVE-2024-10821?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-6f6x-f56q-5xgv
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0