CVE-2025-61982
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA code execution vulnerability exists in the Code Stream directive of OpenCFD OpenFOAM version 2506. The Code Stream functionality, which processes OpenFOAM simulation files and can execute embedded code/commands, fails to properly validate or sandbox malicious simulation files. An attacker can craft a specially designed OpenFOAM file containing malicious code that executes when parsed by the vulnerable component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed OpenFOAM versionRun the 'foamVersion' command or list the OpenFOAM directory (e.g., ls /opt/OpenFOAM/) to view the version folder nameAffected if The version is 2506 (the affected version listed in the summary)
-
Confirm the Code Stream feature is in useSearch for 'codeStream' entries in your OpenFOAM case directories (e.g., find . -name '*' -exec grep -l codeStream {} \;) or inspect constant/ dictionaries for codeStream dictionariesAffected if Code Stream dictionaries or directives are present in any simulation case directories
-
Inspect Code Stream configuration for external command executionExamine any found codeStream dictionaries - look for #codeStream or codeStream blocks that contain executeable commands or system callsAffected if The codeStream configuration includes #include, #! or shell execution syntax
-
Review access to untrusted simulation filesCheck if the OpenFOAM environment processes simulation files from untrusted or external sources, particularly files in 0/, constant/, or system/ directories that were not created locallyAffected if Users import or process OpenFOAM case files from unknown or unverified sources
If OpenFOAM version 2506 is installed, Code Stream functionality is present in any case, and untrusted simulation files can be processed, the environment is potentially affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUsers should refrain from opening or processing untrusted OpenFOAM simulation files, particularly from unknown or unverified sources. Organizations using OpenFOAM should implement file inspection and sandboxing for simulation file processing and monitor for available patches from OpenCFD.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61982 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data