CVE-2026-11958
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 · uneditedLocal privilege escalation by loading DLLs from a shared temporary directory in ANSSI’s DFIR-ORC, versions 10.2.7 and prior. An attacker with prior access to the system, can place a malicious DLL in C:\Windows\Temp and wait for the application to be executed. Because DFIR-ORC is extracted and executed from that location with administrative privileges, the malicious library can be loaded automatically, allowing the attacker to gain administrator privileges on the affected machine.
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 · high confidenceANSSI's DFIR-ORC versions 10.2.7 and prior suffer from a DLL planting vulnerability where the tool is extracted and executed from C:\Windows\Temp with administrative privileges. An attacker with prior system access can place a malicious DLL in this shared temporary directory, which DFIR-ORC will automatically load, enabling local privilege escalation to administrator.
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
- Low
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 DFIR-ORC versionLocate the DFIR-ORC executable on the system and check its version property. Common locations include the installation directory or where the tool was initially extracted. Use 'Get-ItemProperty' or right-click properties to view version info.Affected if The installed version is 10.2.7 or any version prior to 10.2.7, as these are the vulnerable versions mentioned in the CVE.
-
Confirm DFIR-ORC execution pathObserve or check the source location from which DFIR-ORC is being launched. The vulnerability applies when the tool is extracted and executed from C:\Windows\Temp.Affected if DFIR-ORC is being run directly from C:\Windows\Temp or a subdirectory within it, as this is the shared temporary directory where an attacker could plant a malicious DLL.
-
Inspect C:\Windows\Temp for foreign DLLsList all DLL files present in C:\Windows\Temp using 'Get-ChildItem C:\Windows\Temp\*.dll' or File Explorer. Identify any DLLs that are not part of the Windows system or expected DFIR-ORC components.Affected if There are unexpected or suspicious DLL files in C:\Windows\Temp that DFIR-ORC could load, especially if they correspond to common DLL dependencies the tool requires.
-
Verify DFIR-ORC runs with elevated privilegesCheck if DFIR-ORC is being executed with administrative or elevated privileges, which is required for the privilege escalation impact of this vulnerability.Affected if DFIR-ORC is running with administrator-level privileges, as the vulnerability enables local privilege escalation to administrator from this context.
You are affected if DFIR-ORC version 10.2.7 or prior is being executed from C:\Windows\Temp with administrative privileges while foreign DLLs exist in that directory that DFIR-ORC may automatically load.
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.
dbcve · scopedUpdate DFIR-ORC to a patched version that implements secure DLL loading (e.g., using explicit absolute paths, disabling DLL search path, or safe DLL loading mechanisms). Alternatively, ensure the temporary directory is cleared of unauthorized files before running the tool.
Latest version newer than 10.2.7 (check GitHub releases for current stable release)
- Identify the current installed version of ANSSI's DFIR-ORC by checking the executable properties or running 'dfir-orc.exe /version'
- Backup any existing DFIR-ORC configurations, scripts, or customizations in the installation directory
- Download the latest version of ANSSI's DFIR-ORC from the official GitHub repository (github.com/ANSSI-FR/dfir-orc) or the official distribution point
- Replace the existing DFIR-ORC executable and associated files in the installation directory with the updated version
- Verify the new version is installed correctly by running 'dfir-orc.exe /version'
- Ensure the application is not run directly from C:\Windows\Temp; move the installation to a secure, dedicated directory with appropriate access controls
- Restart any scheduled or automated DFIR-ORC tasks to ensure they use the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11958 — 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-2026-11958 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