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
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 10.0Exploit: None knownExposed: 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 PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

April 21, 2026

Last Modified

April 22, 2026

Advisory Details (6)

Auto-updated Sep 12, 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

Client Challenge

https://metacpan.org/release/RURBAN/Storable-3.05/changes
generic

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

https://github.com/Perl/perl5/issues/15831
generic
https://github.com/Perl/perl5/commit/a258c17c6937f79529c8319a829310e09cdbd216.patch

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
perl—5.28.0-3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
perl—5.28.0-3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
perl—5.28.0-3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
perl—5.28.0-3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 25× 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 343 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 1% probability of exploitation in the next 30 days, which ranks it in the top 51.2% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs