CVE-2019-9636

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2019-19005 (ENISA EUVD) · GHSA-v82r-hg27-h4wh (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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: 7.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Python 2.7.x through 2.7.16 and 3.x through 3.7.2 is affected by: Improper Handling of Unicode Encoding (with an incorrect netloc) during NFKC normalization. The impact is: Information disclosure (credentials, cookies, etc. that are cached against a given hostname). The components are: urllib.parse.urlsplit, urllib.parse.urlparse. The attack vector is: A specially crafted URL could be incorrectly parsed to locate cookies or authentication data and send that information to a different host than when parsed correctly. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.7, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.3, v3.7.3rc1, v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
47
EG Risk 47/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation7.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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
7.7%
EPSS %ILE
94th
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
7.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 every mission impact level.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 every mission impact level.

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

Exploitation none (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

March 8, 2019

Last Modified

October 14, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHBA-2019:0959
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHBA-2019:0764
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHBA-2019:0763
Web page

PSIRT.COM — Product Security Incident Response Team

http://www.securityfocus.com/bid/107400

Vendor Advisories for CVE-2019-9636(12)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython2.7-minimal (2.7.3-0ubuntu3.14) @ precise2026-11-01ubuntu
ubuntupython3.5-venv (3.5.2-2ubuntu0~16.04.8) @ xenial2026-11-01ubuntu
ubuntupython3.5-venv (3.5.2-2ubuntu0~16.04.13+esm13) @ xenial2026-11-01ubuntu
redhatpython-0:2.7.5-59.el7_42019-10-23redhat
redhatpython-0:2.7.5-70.el7_52019-10-08redhat
redhatpython-0:2.6.6-68.el6_102019-06-13redhat
redhatpython27:2.7-8000020190410132513.c0efe9782019-05-07redhat
redhatpython3-0:3.6.8-2.el8_02019-05-07redhat
redhatrh-python35-python-0:3.5.1-12.el72019-04-30redhat
redhatpython27-python-0:2.7.13-6.el72019-04-23redhat
redhatredhat-virtualization-host-0:4.2-20190411.1.el7_62019-04-16redhat
redhatrhvm-appliance-0:4.2-20190411.1.el72019-04-16redhat
redhatrh-python36-python-0:3.6.3-7.el72019-04-16redhat
redhatpython-0:2.7.5-77.el7_62019-04-08redhat

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

(14 across 10 ecosystems)
Alpine:v3.7(2)
PackageVulnerable rangeFix by version rangeDependents
python2—
  • every version up to 2.7.15-r2: fixed in 2.7.15-r2
—
python3—
  • every version up to 3.6.8-r0: fixed in 3.6.8-r0
—
Alpine:v3.8(2)
PackageVulnerable rangeFix by version rangeDependents
python2—
  • every version up to 2.7.15-r2: fixed in 2.7.15-r2
—
python3—
  • every version up to 3.6.8-r0: fixed in 3.6.8-r0
—
Debian:8(2)
PackageVulnerable rangeFix by version rangeDependents
python2.72.7.9-2, 2.7.9-2+deb8u1, 2.7.9-2+deb8u2
  • every version up to 2.7.9-2+deb8u3: fixed in 2.7.9-2+deb8u3
—
python3.43.4.2-1, 3.4.2-1+deb8u1, 3.4.2-1+deb8u2
  • every version up to 3.4.2-1+deb8u3: fixed in 3.4.2-1+deb8u3
—
Debian:9(2)
PackageVulnerable rangeFix by version rangeDependents
python2.72.7.13-2, 2.7.13-2+deb9u1, 2.7.13-2+deb9u2, 2.7.13-2+deb9u3
  • every version up to 2.7.13-2+deb9u4: fixed in 2.7.13-2+deb9u4
—
python3.53.5.3-1, 3.5.3-1+deb9u1
  • every version up to 3.5.3-1+deb9u2: fixed in 3.5.3-1+deb9u2
—
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
python2—
  • every version up to 2.7.16-r1: fixed in 2.7.16-r1
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
python2—
  • every version up to 2.7.16-r1: fixed in 2.7.16-r1
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
python2—
  • every version up to 2.7.16-r1: fixed in 2.7.16-r1
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.6.8-r0: fixed in 3.6.8-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
python2—
  • every version up to 2.7.16-r1: fixed in 2.7.16-r1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python2.7—
  • every version up to 2.7.16-2: fixed in 2.7.16-2
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 27× in last 7d / 98× 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 100 of 246 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. None are among the latest 100 rows. The 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-9636?
CVE-2019-9636 is a critical-severity vulnerability; its CVE record was published on March 8, 2019. Python 2.7.x through 2.7.16 and 3.x through 3.7.2 is affected by: Improper Handling of Unicode Encoding (with an incorrect netloc) during NFKC normalization. The impact is: Information disclosure (credentials, cookies, etc. that are cached against a given hostname). The components are:…
When was CVE-2019-9636 made public?
CVE-2019-9636 was made public on March 8, 2019: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on March 8, 2019. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2019-9636 actively exploited?
CVE-2019-9636 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.7% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-9636?
CVE-2019-9636 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-9636?
A fix for CVE-2019-9636 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-9636 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-2019-9636

Explore →

Is Your Infrastructure Affected by CVE-2019-9636?

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

Book a Demo →Browse All CVEs