What happened
RCE in Elasticsearch 1.5.2 via insecure Java deserialization on transport port 9300.
Affected versions
Unknown product: See original advisory Fixed: See vendor advisory.
Why it matters
This source correlation may provide earlier visibility while structured CVE metadata is still being updated.
Detection & mitigation
- Review the original advisory and validate affected versions.
- Apply vendor-provided updates or mitigations when available.
Public PoC references
RepositoryAuthorFirst seenReference
SploitusRCE in Elasticsearch 1.5.2 via insecure Java deserialization on transport port 9300.KitPloit2026-09-03T01:57:46Verifiedfi3ro/CVE-2015-5377Java deserialization exploit for elasticsearch 1.5.2 CVE-2015-5377★ 3fi3ro2020-12-28Verifiedkitploit.comRCE in Elasticsearch 1.5.2 via insecure Java deserialization on transport port 9300.hi2026-09-03T01:57:46CandidateSource timeline
Discovered through SploitusView source ↗
Record history
Record created from the first normalized source observation.
Metadata and source references refreshed.