Skip to content

recorded together · two weakness classes

File and Path Handling and Memory Corruption

10 CVEs

10 CVEs name a weakness of both File and Path Handling and Memory Corruption, too few to compare with chance. The pairing most often behind it is CWE-22 (Path Traversal) with CWE-119 (Memory Buffer Bounds), in 1 CVE.

Every dot is a CVE whose record names a weakness from both classes, neither being the other's parent in the CWE hierarchy. The named ones come first: exploited in the wild, then those with a public check, then the likeliest to be.

CVEs that carry a weakness of both
10
Chance alone would give
about 167
So they are recorded together
too few CVEs to say

A CVE counts when its record names a weakness from each class, neither being the other's parent. It says the two kinds of flaw are recorded together in one vulnerability more or less often than chance: not that one causes the other, and it follows how the people who file CVEs choose CWEs.

How this is weighed, and the sources

Chance is what the two classes' shares of all CVEs that carry weaknesses of two or more classes would give if weaknesses paired at random. A line is drawn on the dial only for pairs with enough CVEs and clearly above chance. Weaknesses are the CWEs the CVE List and NVD record; exploitation is CISA KEV, likelihood is EPSS.

likely to be exploited
1

Every one of the 10 is a mark on the map. Named now: 1 to 10, most at risk first.

  1. The remote management interface on the Claymore Dual GPU miner 10.1 is vulnerable to an authenticated directory traversal vulnerability exploited by issuing a specially crafted re…CVE-2017-16929Claymore Dual Miner Project · 13% likely

    CWE-22

  2. OWASP Dependency-Check before 3.2.0 allows attackers to write to arbitrary files via a crafted archive that holds directory traversal filenames.CVE-2018-12036Owasp · 1.7% likely

    CWE-22Owasp

  3. In Python 3.6 through 3.6.10, 3.7 through 3.7.8, 3.8 through 3.8.4rc1, and 3.9 through 3.9.0b4 on Windows, a Trojan horse python3.dll might be used in cases where CPython is embed…CVE-2020-15523Python · 0.9% likely

    CWE-427Python

  4. Git looks for localized messages in the wrong placeCVE-2023-25815git-for-windows · CVSS 3.3 · 0.8% likely

    CWE-22Git For Windows Project

  5. Unauthenticated file read in Mikrotik RouterOSCVE-2026-67281Mikrotik · CVSS 8.7 · 0.7% likelycovered by CyberSIXT

    CWE-824Mikrotik1 article

  6. Fireware OS Missing Authorization in wgagent Management API Allows Denial of Service - Variant ACVE-2026-86136WatchGuard · CVSS 7.1 · 0.3% likely

    CWE-22WatchGuard

  7. Arbitrary server-side file read in LangSmith SDK TracingMiddlewareCVE-2026-59152langchain-ai · CVSS 5 · 0.2% likely

    CWE-22LangChain AI

  8. PassMark PerformanceTest, BurnInTest, and OSForensics Kernel Null Pointer Dereference via DirectIo64.sys IOCTLCVE-2026-80118PassMark Software · CVSS 7.1 · 0.2% likely

    CWE-476PassMark Software

  9. Composer: Arbitrary file write outside vendor via malicious transitive package nameCVE-2026-59948composer · CVSS 7 · 0.1% likelycovered by CyberSIXT

    CWE-22Composer

  10. bit7z: Path Traversal via Null Byte Injection from `gcount()` Off-by-One in `restoreSymlink()`CVE-2026-45380rikyoz · CVSS 3.6 · 0.1% likely

    CWE-22

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.

Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-15 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.