CVE & CISA-KEV Catalog

CVE-2026-80118

HIGH
7.1
CVSS v3
NVD

Description

PassMark PerformanceTest before 11.1 build 1012, BurnInTest before 11.1 build 1000, and OSForensics before 11.1 build 1016 contain an unauthenticated physical memory disclosure in DirectIo64.sys, reachable by unprivileged local users through a single IOCTL with no caller-identity check. The handler writes a crash-dump-format (PAGEDU64) image of all physical memory to a caller-supplied file path in the SYSTEM context, allowing a standard user to create files in locations they cannot otherwise write and to recover memory belonging to processes of other users. The image is preceded by a header that exposes the kernel loaded-module list, active-process list and PFN database pointers, defeating KASLR. The same handler also dereferences the return value of an internal kernel-structure locator without a NULL check; that locator returns NULL on three distinct failure paths, and a kernel crash results on builds where any of those paths is taken.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityNone

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploit Intelligence

0.11%probability of exploitation in 30 days
2ndpercentile

Low risk: more likely to be exploited than 2% of all known CVEs.

References

Related Vulnerabilities

Other CWE-73 (External Control of File Name or Path) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2022-39952Critical9.8100%-Fix
CVE-2024-8517Critical9.895%-Fix
CVE-2025-33053High8.888%KEVFix
CVE-2023-4634Critical9.886%-Fix
CVE-2024-43451Medium6.584%KEVFix
CVE-2018-17246Critical9.882%-Fix

Common questions

How do I fix CVE-2026-80118?

No published fix for CVE-2026-80118 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-80118 being actively exploited?

Not that we know of. CVE-2026-80118 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.11% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.

How severe is CVE-2026-80118?

CVE-2026-80118 has a CVSS v3 base score of 7.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-80118
CVE-2026-80118 severity badge

Markdown

[![CVE-2026-80118](https://tridentstack.com/cve/badge/CVE-2026-80118.svg)](https://tridentstack.com/cve/CVE-2026-80118)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-80118"><img src="https://tridentstack.com/cve/badge/CVE-2026-80118.svg" alt="CVE-2026-80118"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-10.