CVE-2017-20230

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-21. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 10.0Exploit: NoneExposed: 0

A fix is available — apply it.

Storable versions before 3.05 for Perl has a stack overflow.

The retrieve_hook function stored the length of the class name into a signed integer but in read operations treated the length as unsigned. This allowed an attacker to craft data that could trigger the overflow.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
45(Track)
EG Risk 45/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
Severity100% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
46.9%
KEV
Not listed

Published

April 21, 2026

Last Modified

April 22, 2026

Advisory Details (6)

Auto-updated Jul 17, 2026
No patch confirmed yet.
generic

oss-security - CVE-2017-20230: Storable versions before 3.05 for Perl has a stack overflow

http://www.openwall.com/lists/oss-security/2026/04/21/5
generic

[perl #130635] [PATCH] Stack overflow in Storable retrieve_hook - nntp.perl.org

https://www.nntp.perl.org/group/perl.perl5.porters/2017/01/msg242703.html
generic

[perl #130635] [PATCH] Stack overflow in Storable retrieve_hook - nntp.perl.org

https://www.nntp.perl.org/group/perl.perl5.porters/2017/01/msg242533.html
generic

[PATCH] Stack overflow in Storable retrieve_hook · Issue #15831 · Perl/perl5 · GitHub

https://github.com/Perl/perl5/issues/15831

Vendor Advisories for CVE-2017-20230(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatperl-storable-main-3.37-522.1.hum12026-04-10redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 43× 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 208 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2017-20230?
CVE-2017-20230 is a critical vulnerability published on April 21, 2026. Storable versions before 3.05 for Perl has a stack overflow. The retrieve_hook function stored the length of the class name into a signed integer but in read operations treated the length as unsigned. This allowed an attacker to craft data that could trigger the overflow.
When was CVE-2017-20230 disclosed?
CVE-2017-20230 was first published in the National Vulnerability Database on April 21, 2026, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-20230 actively exploited?
CVE-2017-20230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-20230?
CVE-2017-20230 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2017-20230?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-20230, 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

Explore the affected products and dependency analysis for CVE-2017-20230

Explore →

Is Your Infrastructure Affected by CVE-2017-20230?

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