Skip to main content
VulnerabilityPublished

CVE-2026-123268: libyal libvmdk · Memory Corruption

Affects libyal libvmdkSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 6 Nov 2026, 00:03 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.05.1
CNA (VulDB)CVSS 3.13.5
CNA (VulDB)CVSS 3.03.5
CNA (VulDB)CVSS 2.04.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
libyallibvmdkAffected
  • =3fdd7839758e9f44ef95e1dfccde8552b860a4fc
Fixed in–
GitHublibyal/libvmdkpkg:github/libyal/libvmdkOther threatsAffected
  • *
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:libyal:libvmdk:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the patch identified by commit 175d3fc0a0b961f362f16e7560a6169d7213e16b to remediate the vulnerability. Since libyal uses a rolling release model, ensure your libvmdk installation is updated to the latest commit that includes this fix. No other specific mitigations are indicated.

Description

CVE-2026-123268 is a medium severity memory corruption vulnerability in the libvmdk component of the libyal project. It affects the function libvmdk_extent_table_get_extent_data_file_path in the Extent Data File Handler. The vulnerability can be triggered remotely and has publicly disclosed exploit code. The product uses a rolling release model, so exact affected versions are not specified. A patch identified by commit 175d3fc0a0b961f362f16e7560a6169d7213e16b is available and recommended for remediation.

References

Community reviews

Loading reviews…