CVE-2025-13837

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory (severity: LOW) published 2025-12-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

When loading a plist file, the plistlib module reads data in size specified by the file itself, meaning a malicious file can cause OOM and DoS issues

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

Published

December 1, 2025

Last Modified

September 3, 2026

Advisory Details (9)

Auto-updated Sep 3, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

Mailman 3 [CVE-2025-13837] Out-of-memory when loading Plist - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/2X5IBCJXRQAZ5PSERLHMSJFBHFR3QM2C/
github_pr

gh-119342: Fix a potential denial of service in plistlib

Fix merged in python/cpython PR #119343 on 2025-12-01 — awaiting tagged release

https://github.com/python/cpython/pull/119343
generic

Out-of-memory when loading a Plist · Issue #119342 · python/cpython · GitHub

https://github.com/python/cpython/issues/119342
github_commit

commit cefee7d118a2 (python/cpython)

Fix landed in python/cpython commit cefee7d118a2 — awaiting tagged release

https://github.com/python/cpython/commit/cefee7d118a26ef6cd43db59bb9d98ca9a331111
github_commit

commit b64441e48523 (python/cpython)

Fix landed in python/cpython commit b64441e48523 — awaiting tagged release

https://github.com/python/cpython/commit/b64441e4852383645af5b435411a6f849dd1b4cb
github_commit

commit 71fa8eb8233b (python/cpython)

Fix landed in python/cpython commit 71fa8eb8233b — awaiting tagged release

https://github.com/python/cpython/commit/71fa8eb8233b37f16c88b6e3e583b461b205d1ba
github_commit

commit 694922cf40aa (python/cpython)

Fix landed in python/cpython commit 694922cf40aa — awaiting tagged release

https://github.com/python/cpython/commit/694922cf40aa3a28f898b5f5ee08b71b4922df70
github_commit

commit 5a8b19677d81 (python/cpython)

Fix landed in python/cpython commit 5a8b19677d81 — awaiting tagged release

https://github.com/python/cpython/commit/5a8b19677d818fb41ee55f310233772e15aa1a2b
github_commit

commit 568342cfc8f0 (python/cpython)

Fix landed in python/cpython commit 568342cfc8f0 — awaiting tagged release

https://github.com/python/cpython/commit/568342cfc8f002d9a15f30238f26b9d2e0e79036

Vendor Advisories for CVE-2025-13837(9)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
ubuntupython3.5-venv (3.5.2-2ubuntu0~16.04.4~14.04.1+esm9) @ trusty2026-05-29ubuntu
redhatrhui5/rhua-rhel9:17797982222026-05-27redhat
redhatpython3.12-0:3.12.13-2.el10_22026-05-19redhat
redhatpython3.12-0:3.12.13-2.el9_82026-05-19redhat
redhatpython3.12-0:3.12.13-2.el8_102026-04-27redhat
redhatpython3-11-main-3.11.15-4.hum12026-04-17redhat
redhatpython3-12-main-3.12.13-3.hum12026-04-17redhat
redhatpython3-14-main-3.14.4-1.hum12026-04-11redhat
redhatpython3-13-main-3.13.13-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 4 ecosystems)
Debian:14(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2, 7.3.20+dfsg-1, 7.3.20+dfsg-2, 7.3.20+dfsg-3, 7.3.20+dfsg-47.3.21+dfsg-1—
python3.133.13.5-2, 3.13.6-1, 3.13.7-1, 3.13.8-1, 3.13.9-13.13.11-1—
python3.143.14.0-1 ... 3.14.0~rc3-1 (13 versions)3.14.2-1—
Debian:11(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)——
python3.93.9.2-1, 3.9.2-1+deb11u1, 3.9.2-1+deb11u2, 3.9.2-1+deb11u33.9.2-1+deb11u4—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)——
python3.113.11.2-6 ... 3.11.2-6+deb12u6 (7 versions)3.11.2-6+deb12u7—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.5-23.13.5-2+deb13u1—

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-13837?
CVE-2025-13837 is a medium vulnerability published on December 1, 2025. When loading a plist file, the plistlib module reads data in size specified by the file itself, meaning a malicious file can cause OOM and DoS issues
When was CVE-2025-13837 disclosed?
CVE-2025-13837 was first published in the National Vulnerability Database on December 1, 2025, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-13837 actively exploited?
CVE-2025-13837 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 86.8% of all scored CVEs.
What is the CVSS score of CVE-2025-13837?
CVE-2025-13837 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-13837?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-13837, 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-13837

Explore →

Is Your Infrastructure Affected by CVE-2025-13837?

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

Start Free Scan →Browse All CVEs