How severe is CVE-2014-1830?

No CVSS score has been assigned to CVE-2014-1830 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-1830?

CVE-2014-1830 affects the following packages: requests (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-1830?

Update requests to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1830 is resolved across your whole dependency graph.

How do I detect CVE-2014-1830 in my PyPI dependencies?

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.

How do I mitigate CVE-2014-1830 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2014-1830 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-1830 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-1830?

CVE-2014-1830 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 81th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-1830?

CVE-2014-1830 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-1830 published, and has it been updated?

CVE-2014-1830 was published on October 15, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2014-1830 — requests

CVE-2014-1830 is a Information Exposure vulnerability in requests. A fix is available for requests — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Requests

Also known asGHSA-652x-xj99-gmccPYSEC-2014-14

Published

Oct 15, 2014

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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

Requests (aka python-requests) before 2.3.0 allows remote servers to obtain sensitive information by reading the Proxy-Authorization header in a redirected request.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`requests`	all versions	2.3.0`pip install --upgrade 'requests==2.3.0'`

Affected Products

2 products · 2 configurations

opensuseopensuse

1 version

13.1

Application

requestspython

≤ 2.2.1

range

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update requests to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1830 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Requests (aka python-requests) before 2.3.0 allows remote servers to obtain sensitive information by reading the Proxy-Authorization header in a redirected request.

O3 Security · Impact-Aware SCA

Is CVE-2014-1830 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works