VeraCrypt provides disk encryption with strong security based on TrueCrypt. From 1.26.6 until 1.26.29, file-hosted hidden volume creation forces quick format and the FormatNoFs function in src/Common/Format.c and FormatFat function in src/Common/Fat.c use WriteFile to place raw zeroed sectors at predictable 128 MiB intervals. These writes bypass the normal EncryptDataUnits formatting path, leaving deterministic plaintext markers in an area expected to resemble random ciphertext. The markers can weaken plausible deniability during forensic inspection, although they do not disclose hidden-volume content or reduce the strength of VeraCrypt encryption. This issue is fixed in version 1.26.29.
CVE-2026-54073
This medium-severity CVE scores 4.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.6
- EG Score
- 4.6(medium)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity46% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 21, 2026
Advisory Details (3)
Auto-updated Aug 21, 2026Hidden volume quick format weakens plausible deniability · Advisory · veracrypt/VeraCrypt · GitHub
https://github.com/veracrypt/VeraCrypt/security/advisories/GHSA-jjcr-75w7-58jpVeraCrypt 1.26.29
Patch available: veracrypt/VeraCrypt VeraCrypt_1.26.29
https://github.com/veracrypt/VeraCrypt/releases/tag/VeraCrypt_1.26.29commit 689a59cd584f (veracrypt/VeraCrypt)
Fix landed in veracrypt/VeraCrypt commit 689a59cd584f — awaiting tagged release
https://github.com/veracrypt/VeraCrypt/commit/689a59cd584f090ca5f9214d5f2f3a9eac499e53Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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.
- 2026-08-26 10:23 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 12:23 UTCEG score recompute
- 2026-08-23 16:19 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 20:23 UTCEG score recompute
- 2026-08-21 19:44 UTCEG score recompute
- 2026-08-21 19:21 UTCEG score recompute
- 2026-08-21 19:04 UTCEG score recompute
- 2026-08-21 19:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-693
- CVE-2021-32835EG 9.9EPSS p91CRITICAL
- CVE-2019-10328EG 9.9CRITICAL
- CVE-2019-1003030EG 9.9 KEVEPSS p100CRITICAL
- CVE-2021-27497NVD 6.5EG 9.8CRITICAL
- CVE-2020-10887EG 9.8EPSS p90CRITICAL
- CVE-2017-3197EG 9.8EPSS p92CRITICAL
- CVE-2018-9318EG 9.8EPSS p90CRITICAL
- CVE-2018-9311EG 9.8EPSS p90CRITICAL
- CVE-2017-8864EG 9.8CRITICAL
- CVE-2013-2465EG 9.8 KEVEPSS p100CRITICAL
Frequently asked(5)
What is CVE-2026-54073?
When was CVE-2026-54073 disclosed?
Is CVE-2026-54073 actively exploited?
What is the CVSS score of CVE-2026-54073?
How do I remediate CVE-2026-54073?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54073
Is Your Infrastructure Affected by CVE-2026-54073?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.