Skip to content

← Actionable
High, CVSS 7.5amended

InvokeAI has Denial of Service (DoS) vulnerability in /api/v1/images/upload

CVE-2024-10821GHSA-6f6x-f56q-5xgv

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI invokeai

    Affected
    <= 5.0.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2024-10821: 0.64% estimated exploitation activity in the next 30 days; percentile 50.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-6f6x-f56q-5xgv

  2. Revision 1 · created ·

    Published from osv record GHSA-6f6x-f56q-5xgv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-10821

Advisory: InvokeAI has Denial of Service (DoS) vulnerability in `/api/v1/images/upload`
IDs: CVE-2024-10821, GHSA-6f6x-f56q-5xgv
Record: https://patchnext.com/advisories/cve-2024-10821 (revision 2, source checked 26 Oct 2026, 13:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI invokeai: affected <= 5.0.2

## Suggested inspection (read-only)
- `python -m pip show invokeai`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on invokeai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6f6x-f56q-5xgv (OSV record GHSA-6f6x-f56q-5xgv lists affected ranges: PyPI invokeai >=0 <=5.0.2)
- Verified: https://github.com/advisories/GHSA-6f6x-f56q-5xgv (GitHub-reviewed advisory GHSA-6f6x-f56q-5xgv lists affected ranges: PyPI invokeai >=0 <=5.0.2)

Commands are suggestions: review each one before running it.

Loading voting…