# CVE-2019-9636: Information disclosure in n/a > Attackers can craft URLs to trick Python's urllib into sending sensitive cookies or credentials to the wrong host, leading to information disclosure. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Mar 2019 - **Updated:** 14 Oct 2026 - **Also known as:** ALPINE-CVE-2019-9636, DEBIAN-CVE-2019-9636, GHSA-v82r-hg27-h4wh, MGASA-2019-0148, PSF-2019-9, RHBA-2019:0763, RHBA-2019:0764, RHSA-2019:0710, RHSA-2019:0765, RHSA-2019:0806, RHSA-2019:0902, RHSA-2019:0997, RHSA-2019:1467, RHSA-2019:2980, RHSA-2019:3170, SUSE-SU-2019:0961-1, SUSE-SU-2019:0971-1, UBUNTU-CVE-2019-9636, openSUSE-SU-2019:1282-1 ## What is CVE-2019-9636? CVE-2019-9636 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 8 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-173 (Improper Handling of Alternate Encoding) ## Which versions are affected by CVE-2019-9636? It affects 16 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `python` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.6-68.el6_10 | | `python-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.6-68.el6_10 | | `python-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.6-68.el6_10 | | `python-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.6-68.el6_10 | | `python-test` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.6-68.el6_10 | | `python-tools` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.6-68.el6_10 | | `tkinter` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.6-68.el6_10 | | `python` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.6-68.el6_10 | | `python-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.6-68.el6_10 | | `python-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.6-68.el6_10 | | `python-libs` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.6-68.el6_10 | | `python-test` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.6-68.el6_10 | | `python-tools` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.6-68.el6_10 | | `tkinter` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.6-68.el6_10 | | `python` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.6-68.el6_10 | | `python-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.6-68.el6_10 | | `python-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.6-68.el6_10 | | `python-libs` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.6-68.el6_10 | | `python-test` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.6-68.el6_10 | | `python-tools` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.6-68.el6_10 | | `tkinter` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.6-68.el6_10 | | `python` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.6.6-68.el6_10 | | `python-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.6.6-68.el6_10 | | `python-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.6.6-68.el6_10 | | `python-libs` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.6.6-68.el6_10 | | `python-test` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.6.6-68.el6_10 | | `python-tools` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.6.6-68.el6_10 | | `tkinter` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.6.6-68.el6_10 | | `python` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-77.el7_6 | | `python-debug` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-77.el7_6 | | `python-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-77.el7_6 | | `python-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-77.el7_6 | | `python-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-77.el7_6 | | `python-test` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-77.el7_6 | | `python-tools` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-77.el7_6 | | `tkinter` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.5-77.el7_6 | | `python` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-77.el7_6 | | `python-debug` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-77.el7_6 | | `python-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-77.el7_6 | | `python-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.5-77.el7_6 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Opensuse Leap, Oracle Sun Zfs Storage Appliance Kit, Python Python, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Redhat Openshift Container Platform, Redhat Virtualization. ## How do I fix CVE-2019-9636? Upgrade to a fixed version. ## Is CVE-2019-9636 being exploited? There is no known exploitation of CVE-2019-9636 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-9636 and fix it if it is affected. What it is: CVE-2019-9636 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 8 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-9636 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-9636/ (Markdown: https://insights.sbomify.com/CVE-2019-9636/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-9636 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-9636 - OSV: https://osv.dev/vulnerability/CVE-2019-9636 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-9636/ Summaries are generated and may contain mistakes; the official description above is the record.