CVE-2024-29039

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 1.0% (62nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2024-26088 (ENISA EUVD)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

tpm2 is the source repository for the Trusted Platform Module (TPM2.0) tools. This vulnerability allows attackers to manipulate tpm2_checkquote outputs by altering the TPML_PCR_SELECTION in the PCR input file. As a result, digest values are incorrectly mapped to PCR slots and banks, providing a misleading picture of the TPM state. This issue has been patched in version 5.7.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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
1.0%
EPSS %ILE
62nd
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 (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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

June 28, 2024

Last Modified

November 4, 2025

Advisory Details (4)

Auto-updated Jul 26, 2026
Patch available. Sources: github_release, github.
Web page

[SECURITY] Fedora 39 Update: tpm2-tss-4.0.2-1.fc39 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GI4JFEZBKQQUPJ4RWK6IHEWXAFCEJDPI/
Web page

[SECURITY] Fedora 40 Update: tpm2-tools-5.7-1.fc40 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EFR7SVEWCOXORHPCLLGXEMHFMIGG2MFE/
GitHub advisoryMentions a patch (unverified)

Missing check in tpm2_checkquote allows attackers to misrepresent the TPM state · Advisory · tpm2-software/tpm2-tools · GitHub

https://github.com/tpm2-software/tpm2-tools/security/advisories/GHSA-8rjm-5f5f-h4q6
GitHub release Patch Available

5.7

Patch available: tpm2-software/tpm2-tools 5.7

https://github.com/tpm2-software/tpm2-tools/releases/tag/5.7

Vendor Advisories for CVE-2024-29039(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhattpm2-tools-0:5.2-4.el92024-11-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
tpm2-tools5.0-2 ... 5.7-1 (6 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
tpm2-tools5.4-1, 5.6-1, 5.7-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
tpm2-tools—
  • every version up to 5.7-1: fixed in 5.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
tpm2-tools—
  • every version up to 5.7-1: fixed in 5.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 19× in last 7d / 72× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 97 of 257 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 160 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:40 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  2. 2026-11-01 22:12 UTCEG score recompute
  3. 2026-11-01 22:12 UTCVendor advisory
  4. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  5. 2026-10-31 20:53 UTCEG score recompute
  6. 2026-10-31 20:53 UTCVendor advisory
  7. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  8. 2026-10-30 19:38 UTCEG score recompute
  9. 2026-10-30 19:38 UTCVendor advisory
  10. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  11. 2026-10-29 18:11 UTCEG score recompute
  12. 2026-10-29 18:11 UTCVendor advisory
  13. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  14. 2026-10-28 16:53 UTCEG score recompute
  15. 2026-10-28 16:53 UTCVendor advisory
  16. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  17. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  18. 2026-10-27 15:32 UTCEG score recompute
  19. 2026-10-27 15:32 UTCVendor advisory
  20. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  21. 2026-10-26 13:57 UTCVendor advisory
  22. 2026-10-25 17:14 UTCEG score recompute
  23. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  24. 2026-10-25 12:18 UTCEG score recompute
  25. 2026-10-25 12:18 UTCVendor advisory
Show 72 more
  1. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  2. 2026-10-24 10:57 UTCEG score recompute
  3. 2026-10-24 10:57 UTCVendor advisory
  4. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  5. 2026-10-23 09:41 UTCEG score recompute
  6. 2026-10-23 09:41 UTCVendor advisory
  7. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  8. 2026-10-22 08:25 UTCEG score recompute
  9. 2026-10-22 08:25 UTCVendor advisory
  10. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  11. 2026-10-21 07:09 UTCEG score recompute
  12. 2026-10-21 07:09 UTCVendor advisory
  13. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  14. 2026-10-20 05:53 UTCEG score recompute
  15. 2026-10-20 05:53 UTCVendor advisory
  16. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  17. 2026-10-19 04:38 UTCEG score recompute
  18. 2026-10-19 04:38 UTCVendor advisory
  19. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  20. 2026-10-18 03:22 UTCEG score recompute
  21. 2026-10-18 03:22 UTCVendor advisory
  22. 2026-10-17 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  23. 2026-10-17 02:05 UTCEG score recompute
  24. 2026-10-17 02:05 UTCVendor advisory
  25. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  26. 2026-10-16 00:49 UTCEG score recompute
  27. 2026-10-16 00:49 UTCVendor advisory
  28. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  29. 2026-10-14 19:42 UTCEG score recompute
  30. 2026-10-14 19:42 UTCVendor advisory
  31. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  32. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  33. 2026-10-13 15:51 UTCVendor advisory
  34. 2026-10-12 17:57 UTCEG score recompute
  35. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  36. 2026-10-12 14:34 UTCVendor advisory
  37. 2026-10-11 21:22 UTCEG score recompute
  38. 2026-10-11 16:15 UTCEG score recompute
  39. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  40. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  41. 2026-10-10 15:03 UTCOSV refresh
  42. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  43. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  44. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  45. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  46. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  47. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  48. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  49. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  50. 2026-09-30 19:41 UTCEG score recompute
  51. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  52. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  53. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  54. 2026-09-27 13:43 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  55. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  56. 2026-09-26 00:23 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  57. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  58. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  59. 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  60. 2026-09-21 01:36 UTCOSV refresh
  61. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  62. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  63. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  64. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  65. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  66. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  67. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  68. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  69. 2026-09-11 09:35 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  70. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  71. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  72. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.0% · 60th percentile

Frequently asked(5)

What is CVE-2024-29039?
CVE-2024-29039 is a critical-severity vulnerability; its CVE record was published on June 28, 2024. tpm2 is the source repository for the Trusted Platform Module (TPM2.0) tools. This vulnerability allows attackers to manipulate tpm2_checkquote outputs by altering the TPML_PCR_SELECTION in the PCR input file. As a result, digest values are incorrectly mapped to PCR slots and banks, providing a…
When was the CVE record for CVE-2024-29039 published?
The CVE record for CVE-2024-29039 was published on June 28, 2024. 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 4, 2025; the record at its source may have been updated since.
Is CVE-2024-29039 actively exploited?
CVE-2024-29039 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-29039?
CVE-2024-29039 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2024-29039?
A fix for CVE-2024-29039 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-29039 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-29039

Explore →

Is Your Infrastructure Affected by CVE-2024-29039?

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