# CVE-2024-12882: SSRF in comfyanonymous/comfyui

> Attackers can exploit SSRF in ComfyUI to access unauthorized internal resources and abuse server credentials via specific API endpoints.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-56p4-cfqw-jx4h

## What is CVE-2024-12882?

CVE-2024-12882 is a high-severity server-side request forgery vulnerability in comfyanonymous/comfyui, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

comfyanonymous/comfyui version v0.2.4 suffers from a non-blind Server-Side Request Forgery (SSRF) vulnerability. This vulnerability can be exploited by combining the REST APIs `POST /internal/models/download` and `GET /view`, allowing attackers to abuse the victim server's credentials to access unauthorized web resources.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-12882?

It affects 1 product.


Products: Comfy Comfyui.

## How do I fix CVE-2024-12882?

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

## Is CVE-2024-12882 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-12882 exists.

## Other vulnerabilities in comfyanonymous/comfyui

- [CVE-2024-10481](https://insights.sbomify.com/CVE-2024-10481/): Cross-Site Request Forgery (CSRF) in comfyanonymous/comfyui (medium 6.5)
- [CVE-2024-10099](https://insights.sbomify.com/CVE-2024-10099/): Stored XSS in comfyanonymous/comfyui (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12882 and fix it if it is affected.

What it is: CVE-2024-12882 is a high-severity server-side request forgery vulnerability in comfyanonymous/comfyui, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-12882 exists.

Affected product: comfyanonymous/comfyui. 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-2024-12882/ (Markdown: https://insights.sbomify.com/CVE-2024-12882/index.md)
```

## Sources

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

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