CVE-2025-13151

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-01-08. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
65%
KEV
Not listed

Published

January 7, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 6, 2026
No patch confirmed yet. Sources: cert.
cert

VU#271649 - Stack-based buffer overflow in libtasn1 versions v4.20.0 and earlier

https://www.kb.cert.org/vuls/id/271649
generic

oss-security - Fwd: libtasn1-4.21.0 released [stable] - fixes CVE-2025-13151

http://www.openwall.com/lists/oss-security/2026/01/08/5
generic

Fix for CVE-2025-13151 Buffer overflow (!121) · Merge requests · gnutls / libtasn1 · GitLab

https://gitlab.com/gnutls/libtasn1/-/merge_requests/121
generic

gnutls / libtasn1 · GitLab

https://gitlab.com/gnutls/libtasn1

Vendor Advisories for CVE-2025-13151(9)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhui5/rhua-rhel9:17847950762026-07-23redhat
redhatlibtasn1-0:4.13-6.el8_102026-07-08redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17828905032026-07-01redhat
redhatdiscovery/discovery-ui-rhel9:17827565412026-06-29redhat
redhatlibtasn1-0:4.20.0-5.el10_22026-06-23redhat
redhatlibtasn1-0:4.16.0-10.el9_82026-06-23redhat
ubuntulibtasn1-bin (3.4-3ubuntu0.6+esm1) @ trusty2026-05-29ubuntu
ubuntulibtasn1-doc (4.20.0-2ubuntu0.25.10.1) @ questing2026-05-29ubuntu
redhatlibtasn1-main-4.21.0-1.1.hum12026-04-10redhat

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

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
libtasn1—4.21.0-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
libtasn1—4.21.0-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
libtasn1—4.21.0-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
libtasn1—4.21.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
libtasn1—4.21.0-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libtasn1-64.16.0-2 ... 4.21.0-2 (16 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libtasn1-64.19.0-2 ... 4.21.0-2 (7 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libtasn1-64.20.0-24.20.0-2+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libtasn1-64.20.0-2, 4.21.0-14.21.0-2—

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 / 28× 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 152 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-13151?
CVE-2025-13151 is a high vulnerability published on January 7, 2026. Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1expendoctet_string.
When was CVE-2025-13151 disclosed?
CVE-2025-13151 was first published in the National Vulnerability Database on January 7, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-13151 actively exploited?
CVE-2025-13151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 34.9% of all scored CVEs.
What is the CVSS score of CVE-2025-13151?
CVE-2025-13151 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-13151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-13151, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-13151

Explore →

Is Your Infrastructure Affected by CVE-2025-13151?

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

Start Free Scan →Browse All CVEs