CVE-2026-19566

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th 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: cisa-adp, epss
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Net::CIDR::Set versions before 0.23 for Perl allow memory exhaustion and malformed set ranges via unbounded IPv6 prefix lengths.

The _encode method accepts any prefix length matching (0|[1-9][0-9]*) and passes it to _width2bits(), which builds the mask as '1' x ($width + 8), one character per bit. The _inc() method then unpacks the packed mask into a Perl array of one scalar per byte, so the prefix length alone sets the allocation size: ::/100000000 builds a 100 MB string and a 12.5 million element array. The value being tested is parsed, not just the configured ranges: contains() builds a set from its argument, and _guess_coder() tries the IPv4 coder and then the IPv6 coder, so an IPv4-only set expands an oversized IPv6 prefix length before the mixed address width check rejects it.

Any caller that passes untrusted input to contains() or add() can exhaust process memory. A prefix length above 128 is also stored as a range that does not match the requested block: 2001:db8::/129 stringifies back unchanged, contains() of its own base address returns false, and removing it from a set drops the base address while the set still prints as covering it.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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
0.6%
EPSS %ILE
48th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

August 12, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Aug 12, 2026
Patch available.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libnet-cidr-set-perl0.13-4 ... 0.23-1 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libnet-cidr-set-perl0.15-1 ... 0.23-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libnet-cidr-set-perl0.15-1, 0.19-1, 0.20-1, 0.21-1, 0.22-1
  • every version up to 0.23-1: fixed in 0.23-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× 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.

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

Frequently asked(5)

What is CVE-2026-19566?
CVE-2026-19566 is a high vulnerability published on August 12, 2026. Net::CIDR::Set versions before 0.23 for Perl allow memory exhaustion and malformed set ranges via unbounded IPv6 prefix lengths. The encode method accepts any prefix length matching (0|[1-9][0-9]*) and passes it to width2bits(), which builds the mask as '1' x ($width + 8), one character per bit.…
When was CVE-2026-19566 disclosed?
CVE-2026-19566 was first published on August 12, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19566 actively exploited?
CVE-2026-19566 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19566?
CVE-2026-19566 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-19566?
A fix for CVE-2026-19566 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-19566

Explore →

Is Your Infrastructure Affected by CVE-2026-19566?

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