# CVE-2025-61982: Code injection in OpenFOAM

> Attackers can execute arbitrary code by tricking users into opening a malicious OpenFOAM simulation file, requiring immediate patching.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 18 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-61982, GHSA-f7cx-4c4g-9g59, UBUNTU-CVE-2025-61982

## What is CVE-2025-61982?

CVE-2025-61982 is a high-severity code injection vulnerability in OpenCFD OpenFOAM, published on 18 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An arbitrary code execution vulnerability exists in the Code Stream directive functionality of OpenCFD OpenFOAM 2506. A specially crafted OpenFOAM simulation file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-61982 being exploited?

There is no known exploitation of CVE-2025-61982 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61982 is a high-severity code injection vulnerability in OpenCFD OpenFOAM, published on 18 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-61982 in the wild and no public exploit code.

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

## Sources

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

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