CVE-2015-3253

What it is

The MethodClosure class in runtime/MethodClosure.java in Apache Groovy 1.7.0 through 2.4.3 allows remote attackers to execute arbitrary code or cause a denial of service via a crafted serialized object.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

41.0% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2015-04-10 00:00 UTC ReservedThe CVE id was reserved by its CNA
2. 2015-08-13 14:59 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 00:25 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 41.0% in the next 30 days (EPSS).
• Severity: 9.8 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.
• It meets the bar for Drop everything: critical, and exploited or very likely to be.

Details

Published

2015-08-13 14:59 UTC

Last modified

2026-06-17 00:25 UTC

Exploit probability

41.0% · EPSS, next 30 days

Weakness

CWE-74

Record status

Modified

Affected

• Apache Groovy 1.7.0
• Apache Groovy 1.7.1
• Apache Groovy 1.7.2
• Apache Groovy 1.7.3
• Apache Groovy 1.7.4
• Apache Groovy 1.7.5
• Apache Groovy 1.7.6
• Apache Groovy 1.7.7

Attack profile CVSS 3.0 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2015-3253.md and follow it. Check whether this project is affected by CVE-2015-3253. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge