When was CVE-2015-5400 disclosed?

CVE-2015-5400 was first published in the National Vulnerability Database on September 28, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2015-5400 actively exploited?

CVE-2015-5400 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2015-5400?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-5400, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

CVE-2015-5400

NONECVSS 0.0Elevated

0.0

Squid before 3.5.6 does not properly handle CONNECT method peer responses when configured with cache_peer, which allows remote attackers to bypass intended restrictions and gain access to a backend proxy via a CONNECT request.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 96.2%
KEV: Not listed

References (30)

Is Your Infrastructure Affected by CVE-2015-5400?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2015-5400

Published

Last Modified

References (30)

Data Freshness Timeline

Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2015-5400?

CVE-2015-5400

📅 Published

🔄 Last Modified

🔗 References (30)

Data Freshness Timeline

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2015-5400?

Published

Last Modified

References (30)

Frequently asked(4)