CVE-2015-3253

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 41.0%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 41%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
65(Track*)
EG Risk 65/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation41% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
98.5%
KEV
Not listed

Published

August 13, 2015

Last Modified

May 6, 2026

Advisory Details (3)

Auto-updated May 8, 2026
Patch available.
generic
http://www.securityfocus.com/archive/1/536012/100/0/threaded
generic
http://rhn.redhat.com/errata/RHSA-2016-0066.html
generic Patch Available

The Apache Groovy programming language - Security

http://groovy-lang.org/security.html

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrh-maven33-groovy-0:1.8.9-7.19.el72017-09-05redhat
redhatgroovy-0:1.8.9-8.el7_42017-08-17redhat
redhatgrovy-all2016-06-30redhat
redhatgroovy-all2016-02-03redhat
redhatpatch2015-12-07redhat
redhatpatch2015-12-07redhat
redhatpatch2015-12-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.codehaus.groovy:groovy1.7.0 ... 2.4.3 (99 versions)2.4.4—
org.codehaus.groovy:groovy-all1.7.0 ... 2.4.3 (100 versions)2.4.4—

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 34× 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-23 01:17 UTCEG score recompute
  2. 2026-07-23 00:19 UTCEG score recompute
  3. 2026-07-22 21:58 UTCEG score recompute
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-20 17:03 UTCEPSS rescore
  6. 2026-07-19 14:27 UTCEPSS rescore
  7. 2026-07-19 14:27 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-18 10:00 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 01:56 UTCEPSS rescore
  16. 2026-07-12 05:42 UTCEPSS rescore
  17. 2026-07-11 08:23 UTCEPSS rescore
  18. 2026-07-09 19:05 UTCEPSS rescore
  19. 2026-07-08 15:10 UTCEPSS rescore
  20. 2026-07-07 19:12 UTCOSV refresh
  21. 2026-07-07 13:42 UTCEPSS rescore
  22. 2026-07-06 16:24 UTCEPSS rescore
  23. 2026-07-05 02:26 UTCEPSS rescore
  24. 2026-07-04 06:27 UTCEPSS rescore
  25. 2026-07-02 15:21 UTCEPSS rescore
Show 60 more
  1. 2026-07-01 15:02 UTCEPSS rescore
  2. 2026-07-01 15:02 UTCEPSS rescore
  3. 2026-06-28 04:53 UTCEPSS rescore
  4. 2026-06-27 03:05 UTCEPSS rescore
  5. 2026-06-25 13:47 UTCEPSS rescore
  6. 2026-06-25 13:47 UTCEPSS rescore
  7. 2026-06-24 14:02 UTCEPSS rescore
  8. 2026-06-24 14:02 UTCEPSS rescore
  9. 2026-06-23 21:30 UTCEPSS rescore
  10. 2026-06-22 14:23 UTCEPSS rescore
  11. 2026-06-22 14:22 UTCEPSS rescore
  12. 2026-06-21 01:57 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-19 06:55 UTCOSV refresh
  15. 2026-06-18 17:50 UTCEPSS rescore
  16. 2026-06-18 17:49 UTCEPSS rescore
  17. 2026-06-17 17:49 UTCEPSS rescore
  18. 2026-06-16 17:50 UTCEPSS rescore
  19. 2026-06-16 17:49 UTCEPSS rescore
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-12 23:09 UTCEPSS rescore
  22. 2026-06-11 13:57 UTCEPSS rescore
  23. 2026-06-10 22:15 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
  26. 2026-06-05 22:44 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-05 06:08 UTCEPSS rescore
  29. 2026-06-04 13:10 UTCEPSS rescore
  30. 2026-06-04 13:09 UTCEPSS rescore
  31. 2026-06-02 20:10 UTCEPSS rescore
  32. 2026-06-02 20:10 UTCEPSS rescore
  33. 2026-06-01 13:49 UTCEPSS rescore
  34. 2026-06-01 13:49 UTCEPSS rescore
  35. 2026-05-30 17:23 UTCOSV refresh
  36. 2026-05-29 13:41 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-27 13:38 UTCEPSS rescore
  39. 2026-05-26 07:16 UTCEPSS rescore
  40. 2026-05-26 07:16 UTCEPSS rescore
  41. 2026-05-24 16:43 UTCEPSS rescore
  42. 2026-05-22 21:15 UTCEPSS rescore
  43. 2026-05-22 21:15 UTCEPSS rescore
  44. 2026-05-21 22:40 UTCEPSS rescore
  45. 2026-05-20 22:37 UTCEPSS rescore
  46. 2026-05-20 22:37 UTCEPSS rescore
  47. 2026-05-20 11:21 UTCEPSS rescore
  48. 2026-05-20 11:21 UTCEPSS rescore
  49. 2026-05-20 11:21 UTCEPSS rescore
  50. 2026-05-20 07:06 UTCVendor advisory
  51. 2026-05-20 02:46 UTCVendor advisory
  52. 2026-05-19 22:26 UTCVendor advisory
  53. 2026-05-19 18:06 UTCVendor advisory
  54. 2026-05-19 13:46 UTCVendor advisory
  55. 2026-05-19 09:25 UTCVendor advisory
  56. 2026-05-19 05:05 UTCVendor advisory
  57. 2026-05-19 00:46 UTCEG score recompute
  58. 2026-05-19 00:46 UTCVendor advisory
  59. 2026-05-18 21:30 UTCEPSS rescore
  60. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2015-3253?
CVE-2015-3253 is a critical vulnerability published on August 13, 2015. 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.
When was CVE-2015-3253 disclosed?
CVE-2015-3253 was first published in the National Vulnerability Database on August 13, 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-3253 actively exploited?
CVE-2015-3253 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2015-3253?
CVE-2015-3253 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2015-3253?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-3253, 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-3253

Explore →

Is Your Infrastructure Affected by CVE-2015-3253?

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

Start Free Scan →Browse All CVEs