Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.54% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2023
CVE-2023-45803High confidence
Request body not stripped after redirect in urllib3
urllib3 · urllib3
Official source article: GitHub GHSA-G4MX-Q9VG-27P4 ↗. Check the applicable product and release in the original source.
4.2MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs urllib3 urllib3 and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 3 affected or under-investigation product states without a fixed product state in the same current advisory
Distribution package intelligence
8 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | py3-urllib3 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.26.18-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · main | py3-urllib3 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.26.18-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · main | py3-urllib3 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.26.18-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | python-urllib3 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.26.18-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | python-urllib3 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.26.12-1+deb12u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | python-urllib3 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.26.18-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | python-urllib3 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.26.18-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | python-pip | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 24.0+dfsg-1ubuntu1.3 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Open-source package ranges2 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| pipurllib3 | >= 2.0.0, < 2.0.7 | 2.0.7 | GitHub advisory ↗upstream repository advisory · 4 Nov 2025 |
| pipurllib3 | >= 0, < 1.26.18 | 1.26.18 | GitHub advisory ↗upstream repository advisory · 4 Nov 2025 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2023-45803 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityurllib3: Request body not stripped after redirect from 303 status changes request method to GET
The vendor explicitly identifies these products as affected by this CVE.
- redhat-certification-baremetal-container as a component of Red Hat Certification for Red Hat Enterprise Linux 8
- python-urllib3.src as a component of Red Hat Enterprise Linux 6
- python-pip.src as a component of Red Hat Enterprise Linux 7
- python-s3transfer as a component of Red Hat Enterprise Linux 7
- python-s3transfer.src as a component of Red Hat Enterprise Linux 7
- python-urllib3 as a component of Red Hat Enterprise Linux 7
- python-urllib3.src as a component of Red Hat Enterprise Linux 7
- python3-pip as a component of Red Hat Enterprise Linux 7
- resource-agents as a component of Red Hat Enterprise Linux 7
- resource-agents-aliyun as a component of Red Hat Enterprise Linux 7
- resource-agents-gcp as a component of Red Hat Enterprise Linux 7
- resource-agents-sap as a component of Red Hat Enterprise Linux 7
- Summary
- A flaw was found in urllib3, an HTTP client library for Python. urllib3 doesn't remove the HTTP request body when an HTTP redirect response using status 301, 302, or 303, after changing the method in a request from one that could accept a request body such as `POST` to `GET`, as is required by HTTP RFCs. This issue requires a previously trusted service to become compromised in order to have an impact on confidentiality, therefore, the exploitability of this vulnerability is low. Additionally, many users aren't putting sensitive data in HTTP request bodies; if this is the case, this vulnerability isn't exploitable.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
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.
What
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.
Why
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How
An attacker operating through an adjacent network may attempt exploitation with elevated privileges. If successful, the issue may obtain information outside the intended access boundary.
What
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.
Why
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How
An attacker operating through an adjacent network may attempt exploitation with elevated privileges. If successful, the issue may obtain information outside the intended access boundary.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- an adjacent network → Exposure of Sensitive Information to an Unauthorized Actor → obtain information outside the intended access boundary
- Attack surface
- Adjacent
- Privileges required
- High: elevated access is required
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-200 ↗
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- redhat-certification-baremetal-container as a component of Red Hat Certification for Red Hat Enterprise Linux 8
- python-urllib3.src as a component of Red Hat Enterprise Linux 6
- python-pip.src as a component of Red Hat Enterprise Linux 7
- python-s3transfer as a component of Red Hat Enterprise Linux 7
- python-s3transfer.src as a component of Red Hat Enterprise Linux 7
- python-urllib3 as a component of Red Hat Enterprise Linux 7
- python-urllib3.src as a component of Red Hat Enterprise Linux 7
- python3-pip as a component of Red Hat Enterprise Linux 7
- resource-agents as a component of Red Hat Enterprise Linux 7
- resource-agents-aliyun as a component of Red Hat Enterprise Linux 7
- resource-agents-gcp as a component of Red Hat Enterprise Linux 7
- resource-agents-sap as a component of Red Hat Enterprise Linux 7
- resource-agents-sap-hana as a component of Red Hat Enterprise Linux 7
- resource-agents-sap-hana-scaleout as a component of Red Hat Enterprise Linux 7
- resource-agents.src as a component of Red Hat Enterprise Linux 7
- sap-cluster-connector as a component of Red Hat Enterprise Linux 7
- platform-python-pip as a component of Red Hat Enterprise Linux 8
- python-pip.src as a component of Red Hat Enterprise Linux 8
- python3-pip as a component of Red Hat Enterprise Linux 8
- python3-pip-wheel as a component of Red Hat Enterprise Linux 8
- python-pip.src as a component of Red Hat Enterprise Linux 9
- python3-pip as a component of Red Hat Enterprise Linux 9
- python3-pip-wheel as a component of Red Hat Enterprise Linux 9
- python-urllib3.src as a component of Red Hat OpenShift Data Science (RHODS)
- rhods/odh-ml-pipelines-api-server-rhel8 as a component of Red Hat OpenShift Data Science (RHODS)
- rhods/odh-ml-pipelines-artifact-manager-rhel8 as a component of Red Hat OpenShift Data Science (RHODS)
- rhods/odh-ml-pipelines-cache-rhel8 as a component of Red Hat OpenShift Data Science (RHODS)
- rhods/odh-ml-pipelines-persistenceagent-rhel8 as a component of Red Hat OpenShift Data Science (RHODS)
- rhods/odh-ml-pipelines-scheduledworkflow-rhel8 as a component of Red Hat OpenShift Data Science (RHODS)
- rhods/odh-ml-pipelines-viewercontroller-rhel8 as a component of Red Hat OpenShift Data Science (RHODS)
- and 11 more
- Fixed
- python-urllib3-0:1.25.10-6.el8ost.src as a component of Red Hat OpenStack Platform 17.1
- python3-urllib3-0:1.25.10-6.el8ost.noarch as a component of Red Hat OpenStack Platform 17.1
- python-urllib3-0:1.26.18-0.1.el8pc.src as a component of Red Hat Satellite 6.14 for RHEL 8
- python39-urllib3-0:1.26.18-0.1.el8pc.noarch as a component of Red Hat Satellite 6.14 for RHEL 8
- odf4/cephcsi-rhel9@sha256:5e262fe96badcdebcf0fc40e07acecd607b83a3d48fb90b05bc89ebe790add14_amd64 as a component of RHODF 4.15 for RHEL 9
- odf4/cephcsi-rhel9@sha256:765e623f5b4de11f0482f3abde344df4946665046c9190293a0ae9a5d0d62cd2_s390x as a component of RHODF 4.15 for RHEL 9
- odf4/cephcsi-rhel9@sha256:b4b66a42eb728b46ff977431fd07be976d465680f49516dac3f433cdd12e4dbc_ppc64le as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-core-rhel9@sha256:23becbe8a9d70cda09e2d10fdd3411b943368a3d92535798d595d29b5bbc4f7e_arm64 as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-core-rhel9@sha256:31d951727244d235e62aed00d1121c6f8da4b9d22e895dcfdc814a8545442dac_s390x as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-core-rhel9@sha256:b0eece2979587d7884f8707a6026e28a4aa7a3d96646b01249a9e351acf6b935_ppc64le as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-core-rhel9@sha256:f98634a0fa2517efb383bf6c2a4809f150408225875d7425e64a339209d72e32_amd64 as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-operator-bundle@sha256:19c29de2cf31f95e5f363064095602656355879eb19c778a8655083cebd54ce6_amd64 as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-operator-bundle@sha256:3303677bc0ba2cc5e3f55ae313b516f32378b67a20389f69e09e2c3a9738a87d_s390x as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-operator-bundle@sha256:98fb1b9309d82c663d3118d19fe776de51a277c474a42bf249fdf075f6993bc4_ppc64le as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-rhel9-operator@sha256:93ed7e87e7660991843f3b2114ff2abe74f3b509c2b9a0ee32fc8707051203af_amd64 as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-rhel9-operator@sha256:94f6dded2ff421275b26d147e35d33e383f06ecb04cd0a618d8b4c5046d0e307_ppc64le as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-rhel9-operator@sha256:d04a5a9748ac34459c21d4d10efcc9318220c7ceeeb15c41c56cae9bfbb44872_arm64 as a component of RHODF 4.15 for RHEL 9
- odf4/mcg-rhel9-operator@sha256:d312e5adf2261eeab1106a72565652637d42e2d49d2294cb1413be62697f18d2_s390x as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-console-rhel9@sha256:1add011155a8f31010d52ab3a441a332272ca8bc0bbe93f21d126ed99b07218a_amd64 as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-console-rhel9@sha256:abe77b4860b2c3d88b081aa0bb69c996cb83bc288209aa805de626220cc0ad48_ppc64le as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-console-rhel9@sha256:f1b19a6b805ad0ae2bc7dc08f2e7992e9d440bfa858d5ac2667f9311a95d6e12_s390x as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-operator-bundle@sha256:7fdae4274b87123284a7fb6cc7b56be3e22be629ff834d658a9afd867ef6473b_s390x as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-operator-bundle@sha256:85b41f9c66184ccc262cb8e00d3fdeb9029ca5c39df5521afb44bac604039bbe_amd64 as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-operator-bundle@sha256:b081d99f0507897a3217db22bca57a948bbefdf27e30fd0506275b1dd908c7f6_ppc64le as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-rhel9-operator@sha256:54d229a2b193748da1f66de6ce0c405f591808dd35e26dd0304582d86ba4d708_arm64 as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-rhel9-operator@sha256:d027156f3a8a80a12cfe6bdf207a25a3b1e0e84db9a59853072fdc6ea3766e18_s390x as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-rhel9-operator@sha256:e40c768e57bc8fc19a4028d8474cc00529b05fea3e1fdc7bd793c0b49df4891b_amd64 as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-client-rhel9-operator@sha256:f3b2c47af82b837c2f51cf04d4b7fc973bb3774151d144354d12e9893eadbcef_ppc64le as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-metrics-exporter-rhel9@sha256:378212f323bd7dcc080f31b2f75082ec28c3d6104240c6eb2763d6bd2fc94d8e_s390x as a component of RHODF 4.15 for RHEL 9
- odf4/ocs-metrics-exporter-rhel9@sha256:c89d0ad159bff3915c121a3b97a3dc207d69cab48a25c73e27b53f2aacc6ebf7_ppc64le as a component of RHODF 4.15 for RHEL 9
- and 1538 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 17 Oct 2023 · Last source change 3 Nov 2025, 21:49 UTC · CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2023-0254
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- >= 2.0.0, < 2.0.7; < 1.26.18 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- >= 2.0.0, < 2.0.7; < 1.26.18 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.