CVE-2009-5042

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 1.4% (72nd 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
9.1EG
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: 1.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

python-docutils allows insecure usage of temporary files

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation1.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.4%
EPSS %ILE
72nd
KEV
Not listed

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 none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

October 31, 2019

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Jun 10, 2026
Patch available.
Web page

CVE-2009-5042

https://security-tracker.debian.org/tracker/CVE-2009-5042

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-docutils—
  • every version up to 0.6-2: fixed in 0.6-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-docutils—
  • every version up to 0.6-2: fixed in 0.6-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-docutils—
  • every version up to 0.6-2: fixed in 0.6-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-docutils—
  • every version up to 0.6-2: fixed in 0.6-2
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
docutils0.5
  • 0.5 up to 0.6: fixed in 0.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 24× 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 87 of 129 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. 13 repeat rows among the latest 100 are merged into the row they repeat. The 42 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2009-5042?
CVE-2009-5042 is a critical-severity vulnerability; its CVE record was published on October 31, 2019. python-docutils allows insecure usage of temporary files
When was the CVE record for CVE-2009-5042 published?
The CVE record for CVE-2009-5042 was published on October 31, 2019. 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 21, 2024; the record at its source may have been updated since.
Is CVE-2009-5042 actively exploited?
CVE-2009-5042 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2009-5042?
CVE-2009-5042 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2009-5042?
A fix for CVE-2009-5042 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2009-5042

Explore →

Is Your Infrastructure Affected by CVE-2009-5042?

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

Book a Demo →Browse All CVEs