How severe is CVE-2015-5262?

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

Which packages are affected by CVE-2015-5262?

CVE-2015-5262 affects the following packages: org.apache.httpcomponents:httpclient (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-5262?

Update org.apache.httpcomponents:httpclient to 4.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5262 is resolved across your whole dependency graph.

How do I detect CVE-2015-5262 in my Maven dependencies?

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2015-5262 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-5262 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-2015-5262?

CVE-2015-5262 has an EPSS (Exploit Prediction Scoring System) score of 18.8%, placing it in the 97th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2015-5262?

CVE-2015-5262 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-5262 published, and has it been updated?

CVE-2015-5262 was published on October 27, 2015 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.

☕ Maven

Not in CISA KEV

CVE-2015-5262 — httpclient

CVE-2015-5262 is a CWE-399 vulnerability in org.apache.httpcomponents:httpclient. EPSS puts its 30-day exploitation probability at 18.8% (97th percentile). A fix is available for org.apache.httpcomponents:httpclient — see the affected versions and patch details below.

Denial of service vulnerability in org.apache.httpcomponents:httpclient

Also known asGHSA-fmj5-wv96-r2ch

Published

Oct 27, 2015

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 ↗

18.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.apache.httpcomponents:httpclient

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

Description

http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting during an SSL handshake, which allows remote attackers to cause a denial of service (HTTPS call hang) via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.httpcomponents:httpclient`	all versions	4.3.6`org.apache.httpcomponents:httpclient:4.3.6`

Affected Products

3 products · 7 configurations

Application

httpclientapache

≥ 4.3 && ≤ 4.3.5

range

ubuntu linuxcanonical

3 versions

12.0414.0415.04

fedorafedoraproject

3 versions

212223

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.httpcomponents:httpclient, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.httpcomponents:httpclient to 4.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5262 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-5262 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works