CVE-2025-61982: OpenCFD OpenFOAM · Code Injection
Affects OpenCFD OpenFOAMSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Feb 2026
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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenCFDOpenFOAM | Affected
| Fixed in– |
AI-suggested
1. Immediately restrict the sources of OpenFOAM simulation files to trusted and verified origins; avoid opening files from untrusted or unknown sources. 2. Implement strict file validation and scanning procedures for simulation files before processing, including sandboxing or static analysis to detect malicious code injections. 3. Employ application whitelisting and endpoint protection solutions capable of detecting anomalous code execution behaviors related to OpenFOAM processes. 4. Monitor user activities and file access logs for unusual patterns that may indicate exploitation attempts. 5. Isolate OpenFOAM environments from critical network segments to limit potential lateral movement. 6. Engage with OpenCFD for timely updates and patches; apply vendor-supplied patches as soon as they become available. 7. Educate users on the risks of opening untrusted simulation files and implement policies to reduce user interaction risks. 8. Consider deploying runtime application self-protection (RASP) or behavior-based detection tools to identify exploitation attempts in real time.
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.