CVE & CISA-KEV Catalog

CVE-2026-53762

MEDIUM
6.2
CVSS v3
NVD

Description

VeraCrypt provides disk encryption with strong security based on TrueCrypt. Prior to 1.26.29, non-default builds created with WOLFCRYPT=1 and WOLFCRYPT_BACKEND route SHA-256 and SHA-512 volume-header key derivation through derive_key_sha256 and derive_key_sha512 in src/Crypto/wolfCrypt.c, where the configured iterations value is discarded and wc_HKDF is used instead of PBKDF2-HMAC. Changing the PIM or iteration count therefore does not increase derivation cost, allowing an attacker with an affected container, disk image, or volume header to perform substantially cheaper offline password guesses. Official precompiled VeraCrypt binaries and normal distribution packages use the standard PBKDF2 backend and are not affected. Volumes created by an affected WOLFCRYPT=1 build require backup and recreation because corrected builds derive different keys. This issue is fixed in version 1.26.29.

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 RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityNone
AvailabilityNone

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

Exploit Intelligence

0.06%probability of exploitation in 30 days
0thpercentile

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

References

Related Vulnerabilities

Other CWE-916 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2021-38314Medium5.329%--
CVE-2018-10618Critical9.810%-Fix
CVE-2005-0408Critical9.84.7%--
CVE-2023-33243High8.14.4%--
CVE-2020-14516Critical10.04.1%--
CVE-2024-21754Low1.83.5%-Fix

Common questions

How do I fix CVE-2026-53762?

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

Is CVE-2026-53762 being actively exploited?

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

How severe is CVE-2026-53762?

CVE-2026-53762 has a CVSS v3 base score of 6.2, rated medium. 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-53762
CVE-2026-53762 severity badge

Markdown

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

HTML

<a href="https://tridentstack.com/cve/CVE-2026-53762"><img src="https://tridentstack.com/cve/badge/CVE-2026-53762.svg" alt="CVE-2026-53762"></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-08-26.