CVE-2019-10160

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 5%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

A security regression of CVE-2019-9636 was discovered in python since commit d537ab0ff9767ef024f26246899728f0116b1ec3 affecting versions 2.7, 3.5, 3.6, 3.7 and from v3.8.0a4 through v3.8.0b1, which still allows an attacker to exploit CVE-2019-9636 by abusing the user and password parts of a URL. When an application parses user-supplied URLs to store cookies, authentication credentials, or other kind of information, it is possible for an attacker to provide specially crafted URLs to make the application locate host-related information (e.g. cookies, authentication data) and send them to a different host than where it should, unlike if the URLs had been correctly parsed. The result of an attack may vary based on the application.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
91.9%
KEV
Not listed

Published

June 7, 2019

Last Modified

November 21, 2024

Advisory Details (8)

Auto-updated Jun 8, 2026
Patch available. Sources: redhat, github_commit.
github_commit

commit fd1771dbdd28 (python/cpython)

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

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

commit f61599b050c6 (python/cpython)

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

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

commit 8d0ef0b5edea (python/cpython)

Fix landed in python/cpython commit 8d0ef0b5edea — awaiting tagged release

https://github.com/python/cpython/commit/8d0ef0b5edeae52960c7ed05ae8a12388324f87e
github_commit

commit 250b62acc599 (python/cpython)

Fix landed in python/cpython commit 250b62acc599 — awaiting tagged release

https://github.com/python/cpython/commit/250b62acc59921d399f0db47db3b462cd6037e09
redhat Patch Available

1718388 – (CVE-2019-10160) CVE-2019-10160 python: regression of CVE-2019-9636 due to functional fix to allow port numbers in netloc

Affected: Red Hat Enterprise Linux 5 and 6 as the security regression was not introduced in those versions. See

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10160
redhat Patch Available

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2019:2437
redhat Patch Available

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2019:1587

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.7-venv (3.7.3-2ubuntu0.1) @ disco2026-05-27ubuntu
ubuntupython2.7-minimal (2.7.3-0ubuntu3.14) @ precise2026-05-27ubuntu
ubuntupython3.11-venv (3.11.0~rc1-1~22.04.1~esm1) @ jammy2026-05-27ubuntu
redhatredhat-virtualization-host-0:4.3.5-20190722.0.el7_72019-08-12redhat
redhatpython27-python-0:2.7.16-6.el72019-07-08redhat
redhatpython-0:2.7.5-80.el7_62019-06-20redhat

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(2)

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

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 12× in last 7d / 41× 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.

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

Frequently asked(5)

What is CVE-2019-10160?
CVE-2019-10160 is a critical vulnerability published on June 7, 2019. A security regression of CVE-2019-9636 was discovered in python since commit d537ab0ff9767ef024f26246899728f0116b1ec3 affecting versions 2.7, 3.5, 3.6, 3.7 and from v3.8.0a4 through v3.8.0b1, which still allows an attacker to exploit CVE-2019-9636 by abusing the user and password parts of a URL.…
When was CVE-2019-10160 disclosed?
CVE-2019-10160 was first published in the National Vulnerability Database on June 7, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-10160 actively exploited?
CVE-2019-10160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-10160?
CVE-2019-10160 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-10160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-10160, 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-2019-10160

Explore →

Is Your Infrastructure Affected by CVE-2019-10160?

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