CVE Intelligence
Critical

CVE-2019-10160 — A security regression of CVE-2019-9636 was discovered in python since commit...

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.

Published Jun 7, 2019 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 5.2% (30-day exploitation probability)+14
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
5.23%
ahead of 92% of scored CVEs · Oct 14, 2026
Affects
Canonical
Ubuntu Linux and 13 more
CVSS base
9.8
Critical · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — bugzilla.redhat.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — python-security.readthedocs.io (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 92% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Canonical Ubuntu Linux version 12.04version 14.04version 16.04version 18.04version 19.04 Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 8.0version 9.0 Vulnerable NIST National Vulnerability Database
Fedoraproject Fedora version 30version 31version 29 Vulnerable NIST National Vulnerability Database
Netapp Cloud Backup versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Converged Systems Advisor Agent versions not specified by the source Vulnerable NIST National Vulnerability Database
Opensuse Leap version 15.0version 15.1 Vulnerable NIST National Vulnerability Database
Python Python ≥ 2.7.0 and < 2.7.17≥ 3.5.0 and < 3.5.8≥ 3.6.0 and < 3.6.9≥ 3.7.0 and < 3.7.4version 3.8.0-alpha4version 3.8.0-beta1 Vulnerable NIST National Vulnerability Database
Python Python version affects 2.7, 3.5, 3.6, 3.7, >= v3.8.0a4 and < v3.8.0b1 Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Enterprise Linux Desktop version 7.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Eus version 7.6 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server version 7.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server Aus version 7.6 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server Tus version 7.6 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Workstation version 7.0 Vulnerable NIST National Vulnerability Database
Red Hat Virtualization version 4.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
9.8 CVSS 3.0 Critical 3.9 5.9 secalert@redhat.com via NIST National Vulnerability Database
9.8 CVSS 3.0 Critical — — redhat via CVE Program (cve.org) e CISA ADP
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-172

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 5.23%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · python/python
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2019
  • CVE published
    Jun 7, 2019 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

57 on the record

Elsewhere on this site

Canonical
every CVE for this vendor
CWE-172
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-42169 Gimp: gimp apng loader heap-buffer-overflow when fctl width exceeds ihdr width (file-png.c) Aug 4, 2026
  • CVE-2026-12996 A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote... Jul 30, 2026
  • CVE-2026-15308 Uncontrolled Resource Consumption in Python Jul 9, 2026
  • CVE-2026-14355 Heap-based Buffer Overflow in Php Jul 3, 2026
  • CVE-2026-4360 Tarfile.extract() doesn't fully respect filter parameter Jun 30, 2026
  • CVE-2026-0864 Configuration Injection via Carriage Return (\r) in write() method Jun 23, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2019-10160 is "A security regression of CVE-2019-9636 was discovered in python since commit...", rated Critical. It affects Ubuntu Linux (Canonical); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 5.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.