CVE-2016-6814

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 17% (97th percentile of EPSS-scored CVEs). 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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 17%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

When an application with unsupported Codehaus versions of Groovy from 1.7.0 to 2.4.3, Apache Groovy 2.4.4 to 2.4.7 on classpath uses standard Java serialization mechanisms, e.g. to communicate between servers or to store local data, it was possible for an attacker to bake a special serialized object that will execute code directly when deserialized. All applications which rely on serialization and do not isolate the code which deserializes objects were subject to this vulnerability.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
65
EG Risk 65/100CISA SSVC

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%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
17%
EPSS %ILE
97th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 18, 2018

Last Modified

November 21, 2024

Advisory Details (7)

Auto-updated Oct 7, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:2596
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2017:2486
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:0868
generic
http://rhn.redhat.com/errata/RHSA-2017-0272.html
generic

Pony Mail

http://mail-archives.apache.org/mod_mbox/www-announce/201701.mbox/%3CCADRx3PMZ2hBCGDTY35zYXFGaDnjAs0tc5-upaVs6QN2sYUejyA%40mail.gmail.com%3E
generic

CVE-2016-6814 - PSIRT.COM

http://www.securityfocus.com/bid/95429
generic
http://www.securitytracker.com/id/1039600

Vendor Advisories for CVE-2016-6814(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntugroovy2 (2.4.5-1ubuntu0.1~esm1) @ xenial2026-05-28ubuntu
redhatrh-maven33-groovy-0:1.8.9-7.19.el72017-09-05redhat
redhatgroovy-0:1.8.9-8.el7_42017-08-17redhat
redhatpatch2017-04-03redhat
redhatgroovy2017-02-14redhat

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

(7 across 6 ecosystems)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.codehaus.groovy:groovy1.7.0 ... 2.4.7 (103 versions)
  • 1.7.0 up to 2.4.8: fixed in 2.4.8
—
org.codehaus.groovy:groovy-all1.7.0 ... 2.4.7 (105 versions)
  • 1.7.0 up to 2.4.8: fixed in 2.4.8
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
groovy—
  • every version up to 2.4.8-1: fixed in 2.4.8-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
groovy—
  • every version up to 2.4.8-1: fixed in 2.4.8-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
groovy—
  • every version up to 2.4.8-1: fixed in 2.4.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
groovy—
  • every version up to 2.4.8-1: fixed in 2.4.8-1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
groovy1.8.6-1, 1.8.6-1+deb7u1
  • every version up to 1.8.6-1+deb7u2: fixed in 1.8.6-1+deb7u2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 28× 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.

Showing the most recent 100 of 139 total refreshes for this CVE.

  1. 2026-10-09 20:01 UTCEPSS rescore
  2. 2026-10-08 16:35 UTCEPSS rescore
  3. 2026-10-07 23:40 UTCEPSS rescore
  4. 2026-10-06 15:11 UTCEPSS rescore
  5. 2026-10-05 17:38 UTCEPSS rescore
  6. 2026-10-04 23:17 UTCEPSS rescore
  7. 2026-10-03 14:21 UTCEPSS rescore
  8. 2026-10-03 14:21 UTCEPSS rescore
  9. 2026-09-30 14:58 UTCEPSS rescore
  10. 2026-09-30 09:15 UTCEG score recompute
  11. 2026-09-29 11:23 UTCOSV refresh
  12. 2026-09-28 13:45 UTCEPSS rescore
  13. 2026-09-27 13:40 UTCEPSS rescore
  14. 2026-09-26 15:53 UTCEPSS rescore
  15. 2026-09-26 15:53 UTCEPSS rescore
  16. 2026-09-24 13:59 UTCEPSS rescore
  17. 2026-09-23 13:41 UTCEPSS rescore
  18. 2026-09-20 20:09 UTCEPSS rescore
  19. 2026-09-19 15:35 UTCEPSS rescore
  20. 2026-09-18 19:22 UTCEPSS rescore
  21. 2026-09-17 19:22 UTCEPSS rescore
  22. 2026-09-16 05:05 UTCEPSS rescore
  23. 2026-09-15 03:05 UTCEPSS rescore
  24. 2026-09-13 16:41 UTCEPSS rescore
  25. 2026-09-12 14:55 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:46 UTCEPSS rescore
  2. 2026-09-11 09:31 UTCEPSS rescore
  3. 2026-09-10 09:26 UTCEPSS rescore
  4. 2026-09-09 21:23 UTCOSV refresh
  5. 2026-09-04 13:56 UTCEPSS rescore
  6. 2026-09-02 14:07 UTCEPSS rescore
  7. 2026-09-01 13:48 UTCEPSS rescore
  8. 2026-09-01 03:31 UTCEPSS rescore
  9. 2026-08-28 21:35 UTCEPSS rescore
  10. 2026-08-27 14:20 UTCEPSS rescore
  11. 2026-08-26 14:41 UTCEPSS rescore
  12. 2026-08-25 13:44 UTCEPSS rescore
  13. 2026-08-23 00:38 UTCOSV refresh
  14. 2026-08-21 23:44 UTCEPSS rescore
  15. 2026-08-19 16:59 UTCEPSS rescore
  16. 2026-08-18 13:43 UTCEPSS rescore
  17. 2026-08-17 13:42 UTCEPSS rescore
  18. 2026-08-16 14:51 UTCEPSS rescore
  19. 2026-08-16 02:10 UTCEPSS rescore
  20. 2026-08-15 01:25 UTCEPSS rescore
  21. 2026-08-12 13:46 UTCEPSS rescore
  22. 2026-08-11 13:36 UTCEPSS rescore
  23. 2026-08-08 16:32 UTCEPSS rescore
  24. 2026-08-07 16:22 UTCEPSS rescore
  25. 2026-08-07 03:27 UTCOSV refresh
  26. 2026-08-06 13:42 UTCEPSS rescore
  27. 2026-08-05 19:12 UTCEPSS rescore
  28. 2026-08-04 15:05 UTCEPSS rescore
  29. 2026-08-01 04:11 UTCEPSS rescore
  30. 2026-07-30 16:24 UTCEPSS rescore
  31. 2026-07-28 15:31 UTCEPSS rescore
  32. 2026-07-26 14:50 UTCEPSS rescore
  33. 2026-07-25 14:13 UTCEPSS rescore
  34. 2026-07-24 14:13 UTCEPSS rescore
  35. 2026-07-23 14:15 UTCEPSS rescore
  36. 2026-07-23 01:24 UTCEG score recompute
  37. 2026-07-22 22:03 UTCEG score recompute
  38. 2026-07-22 14:04 UTCEPSS rescore
  39. 2026-07-21 19:18 UTCOSV refresh
  40. 2026-07-21 15:21 UTCEPSS rescore
  41. 2026-07-21 15:21 UTCEPSS rescore
  42. 2026-07-20 17:04 UTCEPSS rescore
  43. 2026-07-19 02:26 UTCEPSS rescore
  44. 2026-07-19 02:26 UTCEPSS rescore
  45. 2026-07-18 10:00 UTCEPSS rescore
  46. 2026-07-18 10:00 UTCEPSS rescore
  47. 2026-07-16 16:59 UTCEPSS rescore
  48. 2026-07-16 16:59 UTCEPSS rescore
  49. 2026-07-15 16:54 UTCEPSS rescore
  50. 2026-07-15 16:54 UTCEPSS rescore
  51. 2026-07-15 01:56 UTCEPSS rescore
  52. 2026-07-13 22:26 UTCEPSS rescore
  53. 2026-07-13 06:09 UTCEPSS rescore
  54. 2026-07-12 05:43 UTCEPSS rescore
  55. 2026-07-12 05:43 UTCEPSS rescore
  56. 2026-07-11 08:24 UTCEPSS rescore
  57. 2026-07-09 19:06 UTCEPSS rescore
  58. 2026-07-08 15:10 UTCEPSS rescore
  59. 2026-07-07 13:42 UTCEPSS rescore
  60. 2026-07-06 16:24 UTCEPSS rescore
  61. 2026-07-06 16:24 UTCEPSS rescore
  62. 2026-07-05 02:27 UTCEPSS rescore
  63. 2026-07-04 14:56 UTCOSV refresh
  64. 2026-07-01 15:02 UTCEPSS rescore
  65. 2026-06-30 23:19 UTCEPSS rescore
  66. 2026-06-30 23:19 UTCEPSS rescore
  67. 2026-06-29 14:03 UTCEPSS rescore
  68. 2026-06-28 14:04 UTCEPSS rescore
  69. 2026-06-28 04:53 UTCEPSS rescore
  70. 2026-06-27 03:05 UTCEPSS rescore
  71. 2026-06-25 13:47 UTCEPSS rescore
  72. 2026-06-24 14:02 UTCEPSS rescore
  73. 2026-06-23 21:30 UTCEPSS rescore
  74. 2026-06-22 14:23 UTCEPSS rescore
  75. 2026-06-21 14:54 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2016-6814?
CVE-2016-6814 is a critical vulnerability published on January 18, 2018. When an application with unsupported Codehaus versions of Groovy from 1.7.0 to 2.4.3, Apache Groovy 2.4.4 to 2.4.7 on classpath uses standard Java serialization mechanisms, e.g. to communicate between servers or to store local data, it was possible for an attacker to bake a special serialized…
When was CVE-2016-6814 disclosed?
CVE-2016-6814 was first published on January 18, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-6814 actively exploited?
CVE-2016-6814 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-6814?
CVE-2016-6814 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-6814?
A fix for CVE-2016-6814 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-6814 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-6814

Explore →

Is Your Infrastructure Affected by CVE-2016-6814?

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

Book a Demo →Browse All CVEs