CVE-2015-5531

NONECVSS 0.09.0▲
EchelonGraph scoreLOW confidence

Score elevated to 9.0 because EPSS predicts 92% probability of exploitation within the next 30 days (top 0.3% of all CVEs). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss
Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 92%
CISA-KEV: Not listedEPSS: 92%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unspecified vectors related to snapshot API calls.

CVSS v3
—
EG Score
9.0(low)
EPSS
99.8%
KEV
Not listed

Published

August 17, 2015

Last Modified

May 6, 2026

References (14)

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.elasticsearch:elasticsearch0.10.0 ... 1.6.0 (122 versions)1.6.1—

Data Freshness Timeline

(refreshed 4× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-09 19:05 UTCEPSS rescore
  2. 2026-07-09 19:05 UTCEPSS rescore
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 02:20 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-30 23:19 UTCEPSS rescore
  8. 2026-06-28 14:04 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-16 17:50 UTCEPSS rescore
  11. 2026-06-16 17:50 UTCEPSS rescore
  12. 2026-06-15 17:45 UTCEPSS rescore
  13. 2026-06-12 23:09 UTCEPSS rescore
  14. 2026-06-12 23:09 UTCEPSS rescore
  15. 2026-06-11 13:57 UTCEPSS rescore
  16. 2026-06-11 13:57 UTCEPSS rescore
  17. 2026-06-10 13:18 UTCEPSS rescore
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-04 13:10 UTCEPSS rescore
  24. 2026-06-02 20:10 UTCEPSS rescore
  25. 2026-05-31 22:28 UTCEPSS rescore
Show 9 more
  1. 2026-05-31 22:28 UTCEPSS rescore
  2. 2026-05-29 13:41 UTCEPSS rescore
  3. 2026-05-28 13:42 UTCEPSS rescore
  4. 2026-05-28 13:42 UTCEPSS rescore
  5. 2026-05-23 00:03 UTCEG score recompute
  6. 2026-05-22 21:15 UTCEPSS rescore
  7. 2026-05-21 22:40 UTCEPSS rescore
  8. 2026-05-18 21:30 UTCEPSS rescore
  9. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCMoCh3n/CVE-2015-5531-POC
    First seen Sep 21, 2022
    Open source ↗
  • Exploit-DBEDB-38383
    First seen Oct 2, 2015

    ElasticSearch 1.6.0 - Arbitrary File Download

    Open source ↗
  • Metasploitauxiliary/scanner/http/elasticsearch_traversal✓ verified
    First seen Jan 1, 2015

    ElasticSearch Snapshot API Directory Traversal

    Open source ↗
  • Nucleihttp/cves/2015/CVE-2015-5531.yaml
    First seen Jan 1, 2015

    ElasticSearch <1.6.1 - Local File Inclusion

    Open source ↗

Frequently asked(4)

What is CVE-2015-5531?
CVE-2015-5531 is a none vulnerability published on August 17, 2015. Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unspecified vectors related to snapshot API calls.
When was CVE-2015-5531 disclosed?
CVE-2015-5531 was first published in the National Vulnerability Database on August 17, 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-5531 actively exploited?
CVE-2015-5531 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2015-5531?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-5531, 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.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-5531

Explore →

Is Your Infrastructure Affected by CVE-2015-5531?

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

Start Free Scan →Browse All CVEs