urllib3 is a user-friendly HTTP client library for Python. urllib3 previously wouldn't remove the HTTP request body when an HTTP redirect response using status 301, 302, or 303 after the request had its method changed from one that could accept a request body (like POST) to GET as is required by HTTP RFCs. Although this behavior is not specified in the section for redirects, it can be inferred by piecing together information from different sections and we have observed the behavior in other major HTTP client implementations like curl and web browsers. Because the vulnerability requires a previously trusted service to become compromised in order to have an impact on confidentiality we believe the exploitability of this vulnerability is low. Additionally, many users aren't putting sensitive data in HTTP request bodies, if this is the case then this vulnerability isn't exploitable. Both of the following conditions must be true to be affected by this vulnerability: 1. Using urllib3 and submitting sensitive information in the HTTP request body (such as form data or JSON) and 2. The origin service is compromised and starts redirecting using 301, 302, or 303 to a malicious peer or the redirected-to service becomes compromised. This issue has been addressed in versions 1.26.18 and 2.0.7 and users are advised to update to resolve this issue. Users unable to update should disable redirects for services that aren't expecting to respond with redirects with redirects=False and disable automatic redirects with redirects=False and handle 301, 302, and 303 redirects manually by stripping the HTTP request body.
CVE-2023-45803
“—” beside the score: it is equal to NVD's CVSS score.
This medium-severity CVE scores 4.2 under NVD CVSS v3. EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.2
- EG Score
- 4.2MEDIUMmedium confidence
- EG Risk
- 19EG Risk 19/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)Severity42% × 45%Impact severity (EG Severity): CVSS 4.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 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
- 0.6%
- EPSS %ILE
- 47th
- 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 (4.2): severity, escalated by confirmed exploitation. This CVE's 4.2 is its impact severity (EG Severity), not escalated.
- EG Severity
- 4.2 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS. 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: 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.
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
October 17, 2023
Last Modified
June 17, 2026
References (7)
- security-advisories@github · CVE Programhttps://github.com/urllib3/urllib3/commit/4e98d57809dacab1cbe625fddeec1a290c478ea9Patch
- security-advisories@github · CVE Programhttps://github.com/urllib3/urllib3/security/advisories/GHSA-g4mx-q9vg-27p4Third Party Advisory
- security-advisories@github · CVE Programhttps://lists.fedoraproject.org/archives/list/[email protected]/message/4R2Y5XK3WALSR3FNAGN7JBYV2B343ZKB/
- security-advisories@github · CVE Programhttps://lists.fedoraproject.org/archives/list/[email protected]/message/5F5CUBAN5XMEBVBZPHFITBLMJV5FIJJ5/
- security-advisories@github · CVE Programhttps://lists.fedoraproject.org/archives/list/[email protected]/message/PPDPLM6UUMN55ESPQWJFLLIZY4ZKCNRX/Mailing List
- security-advisories@github · CVE Programhttps://www.rfc-editor.org/rfc/rfc9110.html#name-getThird Party Advisory
- CVE Programhttps://lists.debian.org/debian-lts-announce/2024/12/msg00020.html
Vendor Advisories for CVE-2023-45803(14)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2025:1793Red Hat Product SecurityMedium
Red Hat Security Advisory: python3.11-urllib3 security update
- RHSA-2025:1813Red Hat Product SecurityMedium
Red Hat Security Advisory: python3.11-urllib3 security update
- RHSA-2025:0078Red Hat Product SecurityMedium
Red Hat Security Advisory: python3.11-urllib3 security update
- RHSA-2024:11238Red Hat Product SecurityMedium
Red Hat Security Advisory: python3.11-urllib3 security update
- RHSA-2024:11189Red Hat Product SecurityMedium
Red Hat Security Advisory: python3.11-urllib3 security update
- RHSA-2024:2988Red Hat Product SecurityMedium
Red Hat Security Advisory: container-tools:rhel8 security update
- RHSA-2024:2968Red Hat Product SecurityMedium
Red Hat Security Advisory: fence-agents security and bug fix update
- RHSA-2024:2952Red Hat Product SecurityMedium
Red Hat Security Advisory: resource-agents security and bug fix update
- +6 more
Patch Availability(20)
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
(16 across 16 ecosystems)
Alpine:v3.15(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Alpine:v3.16(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Alpine:v3.17(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Alpine:v3.18(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| py3-urllib3 | — |
| — |
Debian:10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-urllib3 | 1.24.1-1, 1.24.1-1+deb10u1 |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-urllib3 | 1.26.5-1~exp1 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-urllib3 | 1.26.12-1 |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-urllib3 | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-urllib3 | — |
| — |
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| urllib3 | 0.2 ... 2.0.6 (87 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(9)
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.
- Red HatRHSA-2023:7851MODERATE2023-10-13
RHSA-2023:7851 — Moderate
- Red HatRHSA-2024:0116MODERATE2023-10-13
RHSA-2024:0116 — Moderate
- Red HatRHSA-2024:0300MODERATE2023-10-13
RHSA-2024:0300 — Moderate
- Red HatRHSA-2024:0464MODERATE2023-10-13
RHSA-2024:0464 — Moderate
- Red HatRHSA-2024:0588MODERATE2023-10-13
RHSA-2024:0588 — Moderate
- Red HatRHSA-2024:2734MODERATE2023-10-13
RHSA-2024:2734 — Moderate
- UbuntuUSN-6473-1MEDIUM
urllib3 vulnerabilities
- UbuntuUSN-6473-2MEDIUM
pip vulnerabilities
- UbuntuUSN-7762-1MEDIUM
pip vulnerabilities
Data Freshness Timeline
(refreshed 8× in last 7d / 33× 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 91 of 205 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. 9 repeat rows among the latest 100 are merged into the row they repeat. The 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-10-18 07:48 UTCEG score recompute
- 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-12 21:24 UTCOSV refresh
- 2026-10-12 18:17 UTCEG score recompute
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-11 21:43 UTCEG score recompute
- 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 66 moreShow fewer
- 2026-09-30 16:32 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-22 19:09 UTCOSV refresh
- 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-21 20:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-17 19:25 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-03 15:29 UTCOSV refresh
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-01 04:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-24 14:14 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-17 04:53 UTCOSV refresh
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-10 23:57 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-08-01 23:36 UTCOSV refresh
- 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.15:py3-urllib3 · Alpine:v3.20:py3-urllib3 · Debian:10:python-urllib3
Same vendor
10 shownredhat:RHSA-2023:7851 · redhat:RHSA-2024:1155 · redhat:RHSA-2024:2988
Frequently asked(5)
What is CVE-2023-45803?
When was the CVE record for CVE-2023-45803 published?
Is CVE-2023-45803 actively exploited?
What is the CVSS score of CVE-2023-45803?
How do I remediate CVE-2023-45803?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-45803
Is Your Infrastructure Affected by CVE-2023-45803?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.