CVE-2024-10821VulnerabilityPublished 20 Mar 2025Updated 15 Oct 2025

CVE-2024-10821: invoke-ai/invokeai · Loop with Unreachable Exit Condition

Affects invoke-ai/invokeaiSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubinvoke-ai/invokeai`pkg:github/invoke-ai/invokeai`Other threats	Affected =5.0.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should focus on implementing strict input validation on multipart request boundaries to detect and reject malformed or excessively long boundary strings before processing. 2. Deploy rate limiting and request throttling on the /api/v1/images/upload endpoint to reduce the risk of resource exhaustion from repeated malicious requests. 3. Monitor server resource utilization and configure alerts for unusual CPU or memory spikes indicative of an ongoing attack. 4. Isolate the Invoke-AI service in a container or sandboxed environment with resource limits (CPU, memory) to prevent system-wide impact. 5. If possible, restrict access to the upload endpoint via network controls such as IP whitelisting or VPN access to reduce exposure. 6. Stay updated with Invoke-AI vendor communications for official patches or security updates addressing this vulnerability and apply them promptly once available. 7. Consider implementing Web Application Firewall (WAF) rules to detect and block suspicious multipart boundary patterns. 8. Conduct regular security assessments and penetration tests focusing on multipart request handling to identify similar weaknesses.

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`.

Impact

For European organizations, the primary impact of CVE-2024-10821 is the disruption of AI image generation services provided by Invoke-AI servers. This can lead to significant operational downtime, especially for companies integrating Invoke-AI into their workflows or customer-facing applications. The denial of service can halt business processes, delay project timelines, and degrade user experience. Organizations in sectors such as digital media, creative industries, research institutions, and AI development firms are particularly vulnerable. The lack of authentication requirement means attackers can launch attacks at scale from anywhere, increasing the risk of widespread service outages. Additionally, resource exhaustion on servers may lead to collateral impacts on other hosted services if infrastructure is shared. While no data breach or integrity compromise is indicated, the availability loss can cause reputational damage and financial losses. European entities with public-facing Invoke-AI endpoints are at heightened risk, especially if they lack robust network-level protections or input validation controls.

References

huntr.com/bounties/0ac24835-c4c0-4f11-938a-d5641dfb80b2 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 13:18 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats