CVE-2025-49133

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% 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, nvd
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

Libtpms is a library that targets the integration of TPM functionality into hypervisors, primarily into Qemu. Libtpms, which is derived from the TPM 2.0 reference implementation code published by the Trusted Computing Group, is prone to a potential out of bounds (OOB) read vulnerability. The vulnerability occurs in the ‘CryptHmacSign’ function with an inconsistent pairing of the signKey and signScheme parameters, where the signKey is ALG_KEYEDHASH key and inScheme is an ECC or RSA scheme. The reported vulnerability is in the ‘CryptHmacSign’ function, which is defined in the "Part 4: Supporting Routines – Code" document, section "7.151 - /tpm/src/crypt/CryptUtil.c ". This vulnerability can be triggered from user-mode applications by sending malicious commands to a TPM 2.0/vTPM (swtpm) whose firmware is based on an affected TCG reference implementation. The effect on libtpms is that it will cause an abort due to the detection of the out-of-bounds access, thus for example making a vTPM (swtpm) unavailable to a VM. This vulnerability is fixed in 0.7.12, 0.8.10, 0.9.7, and 0.10.1.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
27(Track)
EG Risk 27/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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 10, 2025

Last Modified

November 3, 2025

References (5)

Vendor Advisories for CVE-2025-49133(7)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibtpms0 (0.9.3-0ubuntu4.25.04.1) @ plucky2026-05-30ubuntu
redhatlibtpms-0:0.9.6-11.el10_02025-09-23redhat
redhatvirt:rhel-8100020250722092921.489197e62025-08-04redhat
redhatvirt:rhel-8060020250716064909.ad008a3a2025-07-30redhat
redhatvirt:rhel-8080020250715121528.63b345852025-07-30redhat
redhatlibtpms-0:0.9.1-5.20211126git1ff6fe1f43.el9_62025-07-29redhat
redhatlibtpms-0:0.9.1-5.20211126git1ff6fe1f43.el9_22025-07-29redhat
redhatlibtpms-0:0.9.1-5.20211126git1ff6fe1f43.el9_42025-07-29redhat

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 6× in last 7d / 37× 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.

Showing the most recent 100 of 106 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-49133?
CVE-2025-49133 is a medium vulnerability published on June 10, 2025. Libtpms is a library that targets the integration of TPM functionality into hypervisors, primarily into Qemu. Libtpms, which is derived from the TPM 2.0 reference implementation code published by the Trusted Computing Group, is prone to a potential out of bounds (OOB) read vulnerability. The…
When was CVE-2025-49133 disclosed?
CVE-2025-49133 was first published in the National Vulnerability Database on June 10, 2025, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-49133 actively exploited?
CVE-2025-49133 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 96.6% of all scored CVEs.
What is the CVSS score of CVE-2025-49133?
CVE-2025-49133 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2025-49133?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-49133, 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-2025-49133

Explore →

Is Your Infrastructure Affected by CVE-2025-49133?

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

Start Free Scan →Browse All CVEs