# CVE-2025-31114: Fooocus webui vulnerable to Remote Code Execution

> Attackers with web UI access can execute arbitrary code via unsafe eval in metadata processing, requiring immediate attention from Fooocus users.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 17 Aug 2026

## What is CVE-2025-31114?

CVE-2025-31114 is a critical code injection vulnerability in lllyasviel Fooocus, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Fooocus is an image generating software. In versions 2.5.5 and prior, the Fooocus web UI is vulnerable to remote code execution due to the unsafe use of eval when processing metadata JSON. An attacker with access to the Fooocus web UI may be able to execute arbitrary code on the instance. As of time of publication, no known patched versions are available, but a suggested fix pull request is available.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2025-31114?


## How do I fix CVE-2025-31114?

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

## Is CVE-2025-31114 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31114 and fix it if it is affected.

What it is: CVE-2025-31114 is a critical code injection vulnerability in lllyasviel Fooocus, published on 11 Aug 2026. 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-2025-31114 exists.

Affected product: lllyasviel Fooocus. 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-2025-31114/ (Markdown: https://insights.sbomify.com/CVE-2025-31114/index.md)
```

## Sources

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

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