CVE-2026-12087

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

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

A fix is available — apply it.

Socket versions before 2.041 for Perl have an out-of-bounds heap read.

In Socket.xs, pack_ip_mreq_source() checks the length of its source argument before the argument is read, so the check tests the byte length carried over from the preceding multiaddr argument instead. Both addresses occupy a 4-byte field, so a valid multiaddr lets a source of any length pass the check, and the source is then copied into the 4-byte imr_sourceaddr field with a fixed-size copy. A source shorter than 4 bytes is not rejected, and the copy reads up to 3 bytes past the end of its buffer.

Calling pack_ip_mreq_source() with a source value shorter than 4 bytes copies adjacent heap memory into the returned packed structure.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
31.5%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 16, 2026

Advisory Details (3)

Auto-updated Jun 16, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-12087: Socket versions before 2.041 for Perl have an out-of-bounds heap read

http://www.openwall.com/lists/oss-security/2026/06/15/10

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatperl-socket-main-2.041-1.hum12026-04-28redhat

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(2)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 300× 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 362 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-12087?
CVE-2026-12087 is a critical vulnerability published on June 15, 2026. Socket versions before 2.041 for Perl have an out-of-bounds heap read. In Socket.xs, packipmreqsource() checks the length of its source argument before the argument is read, so the check tests the byte length carried over from the preceding multiaddr argument instead. Both addresses occupy a 4-byte…
When was CVE-2026-12087 disclosed?
CVE-2026-12087 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12087 actively exploited?
CVE-2026-12087 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12087?
CVE-2026-12087 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-12087?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12087, 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-2026-12087

Explore →

Is Your Infrastructure Affected by CVE-2026-12087?

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