Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

GHSA-9hjg-9r4m-mvj7 — requests

MEDIUMFix: psf/requests#6965

GHSA-9hjg-9r4m-mvj7 is a medium-severity (CVSS 5.3) CWE-522 vulnerability in requests. A fix is available for requests — see the affected versions and patch details below.

Requests vulnerable to .netrc credentials leak via malicious URLs

Also known asCVE-2024-47081PYSEC-2026-1872
Published
Jun 9, 2025
Updated
Sep 10, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9hjg-9r4m-mvj7.

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-9hjg-9r4m-mvj7 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
🐍requests

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Due to a URL parsing issue, Requests releases prior to 2.32.4 may leak .netrc credentials to third parties for specific maliciously-crafted URLs.

Workarounds

For older versions of Requests, use of the .netrc file can be disabled with trust_env=False on your Requests Session (docs).

References

https://github.com/psf/requests/pull/6965 https://seclists.org/fulldisclosure/2025/Jun/2

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIrequestsall versions2.32.4pip install --upgrade 'requests==2.32.4'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for requests, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update requests to 2.32.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9hjg-9r4m-mvj7 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9hjg-9r4m-mvj7 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-9hjg-9r4m-mvj7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat Enterprise Linux 10python-requests-0:2.32.4-1.el10_0RHSA-2025:13604
Red Hat Enterprise Linux 8fence-agents-0:4.2.1-129.el8_10.14RHSA-2025:14750
Red Hat Enterprise Linux 8resource-agents-0:4.9.0-54.el8_10.16RHSA-2025:14999
Red Hat Enterprise Linux 8python-requests-0:2.20.0-6.el8_10RHSA-2025:13234
Red Hat Enterprise Linux 8.2 Advanced Update Supportpython-requests-0:2.20.0-3.el8_2RHSA-2025:15723
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Supportfence-agents-0:4.2.1-65.el8_4.21RHSA-2025:15622
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Supportresource-agents-0:4.1.1-90.el8_4.20RHSA-2025:15618
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Supportpython-requests-0:2.20.0-3.el8_4RHSA-2025:15691

Frequently Asked Questions

### Impact Due to a URL parsing issue, Requests releases prior to 2.32.4 may leak .netrc credentials to third parties for specific maliciously-crafted URLs. ### Workarounds For older versions of Requests, use of the .netrc file can be disabled with `trust_env=False` on your Requests Session ([docs](https://requests.readthedocs.io/en/latest/api/#requests.Session.trust_env)). ### References https://github.com/psf/requests/pull/6965 https://seclists.org/fulldisclosure/2025/Jun/2
O3 Security · Impact-Aware SCA

Is GHSA-9hjg-9r4m-mvj7 in your dependencies?

O3 Security finds GHSA-9hjg-9r4m-mvj7 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-9hjg-9r4m-mvj7: requests (Medium 5.3) | O3 Security