CVE-2026-53762

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.2
EG Score
6.2(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity62% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

August 21, 2026

Last Modified

August 21, 2026

Advisory Details (3)

Auto-updated Aug 21, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github Patch Available🟡 PoC Available

wolfCrypt backend bypasses VeraCrypt PBKDF2 iteration count (non-default WOLFCRYPT=1 builds) · Advisory · veracrypt/VeraCrypt · GitHub

https://github.com/veracrypt/VeraCrypt/security/advisories/GHSA-94c6-mgmv-mqc5
github_release Patch Available

VeraCrypt 1.26.29

Patch available: veracrypt/VeraCrypt VeraCrypt_1.26.29

https://github.com/veracrypt/VeraCrypt/releases/tag/VeraCrypt_1.26.29
github_commit

commit 39f93910075e (veracrypt/VeraCrypt)

Fix landed in veracrypt/VeraCrypt commit 39f93910075e — awaiting tagged release

https://github.com/veracrypt/VeraCrypt/commit/39f93910075e1cf492fcf4a9f99a53c7d0b96b87

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 10:59 UTCEG score recompute
  2. 2026-08-23 15:11 UTCEG score recompute
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 19:21 UTCEG score recompute
  5. 2026-08-21 19:04 UTCEG score recompute
  6. 2026-08-21 19:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53762?
CVE-2026-53762 is a medium vulnerability published on August 21, 2026. VeraCrypt provides disk encryption with strong security based on TrueCrypt. Prior to 1.26.29, non-default builds created with WOLFCRYPT=1 and WOLFCRYPTBACKEND route SHA-256 and SHA-512 volume-header key derivation through derivekeysha256 and derivekeysha512 in src/Crypto/wolfCrypt.c, where the…
When was CVE-2026-53762 disclosed?
CVE-2026-53762 was first published in the National Vulnerability Database on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53762 actively exploited?
CVE-2026-53762 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 100.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53762?
CVE-2026-53762 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-53762?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53762, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53762

Explore →

Is Your Infrastructure Affected by CVE-2026-53762?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs