CVE-2026-77372

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-117192 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

VeraCrypt provides disk encryption with strong security based on TrueCrypt. Prior to 1.26.30, the Unix, macOS, and FreeBSD serialization paths in src/Platform/Serializer.cpp and src/Volume/VolumePassword.cpp accept untrusted length and count values when deserializing data that can cross from the unprivileged GUI or CLI to the root CoreService helper. Serializer::DeserializeWString allocates floor(size / sizeof(wchar_t)) elements but reads size bytes, so a non-aligned size can overflow the heap allocation. VolumePassword::Deserialize accepts PasswordSize values larger than the fixed 128-byte PasswordBuffer, allowing downstream DataPtr() and Size() consumers such as the KDF to read beyond the buffer. DeserializeString, DeserializeWString, and the string and wide-string list readers also lack allocation and collection bounds, which can exhaust memory, and a zero-length DeserializeString can access an empty vector. Windows uses a different path, and the immediate CoreService pipe writer is the same-user parent process, so the documented exposure is a local defense-in-depth boundary rather than a remote attack. This issue is fixed in 1.26.30.

CVSS
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 4, 2026

Last Modified

November 12, 2026

Advisory Details (3)

Auto-updated Nov 4, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

VeraCrypt 1.26.30

Patch available: veracrypt/VeraCrypt VeraCrypt_1.26.30

https://github.com/veracrypt/VeraCrypt/releases/tag/VeraCrypt_1.26.30
GitHub commit

commit fb9d96c52dac (veracrypt/VeraCrypt)

Fix landed in veracrypt/VeraCrypt commit fb9d96c52dac — awaiting tagged release

https://github.com/veracrypt/VeraCrypt/commit/fb9d96c52dace4d34c5427402b512e8de5f832d6
GitHub advisoryMentions a patch (unverified)

Heap overflow and out-of-bounds read in Serializable deserialization (elevated Core service input path) · Advisory · veracrypt/VeraCrypt · GitHub

https://github.com/veracrypt/VeraCrypt/security/advisories/GHSA-4j3p-7hp7-xw73

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 8× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 22:28 UTCEchelonGraph re-scored
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-11-09 22:17 UTCEchelonGraph re-scored
  5. 2026-11-08 16:40 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-11-07 16:39 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-11-06 16:39 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-11-05 16:38 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-11-05 00:03 UTCENISA EUVD ID recordedEUVD-2026-117192 · Source: ENISA EUVD
  10. 2026-11-04 23:27 UTCEchelonGraph re-scored
  11. 2026-11-04 23:00 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
  12. 2026-11-04 22:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77372?
CVE-2026-77372 is a high-severity vulnerability; its CVE record was published on November 4, 2026. VeraCrypt provides disk encryption with strong security based on TrueCrypt. Prior to 1.26.30, the Unix, macOS, and FreeBSD serialization paths in src/Platform/Serializer.cpp and src/Volume/VolumePassword.cpp accept untrusted length and count values when deserializing data that can cross from the…
When was the CVE record for CVE-2026-77372 published?
The CVE record for CVE-2026-77372 was published on November 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-77372 actively exploited?
CVE-2026-77372 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77372?
CVE-2026-77372 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77372?
A fix for CVE-2026-77372 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-77372?

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

Book a Demo →Browse All CVEs