CVE-2026-49942 json
Net::CIDR::Set versions through 0.20 for Perl did not validate network masks
published 5mo ago modified 3mo ago also EUVD-2026-34299
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
Net::CIDR::Set versions through 0.20 for Perl did not validate network masks.
The mask portion of a network mask could contain Unicode digits such as the Arabic-Indic One (U+0661), or non-digits, which were ignored. This could allow network masks to accept larger networks.
Leading zeros were also accepted, but treated as decimal instead of octal. This could lead to confusion about what networks are acceptable.
Patch / fix
- rrwo net::cidr::set 0.21
- libnet-cidr-set-perl Debian 13 0.15-1+deb13u1
- libnet-cidr-set-perl Debian 14 0.21-1
debian advisories DEBIAN-CVE-2026-49942
Is CVE-2026-49942 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
Affected products
- RRWO Net::CIDR::Set
Classification
- Weakness
-
- CWE-1289 Improper Validation of Unsafe Equivalence in Input
References
-
metacpan.org
/release/RRWO/Net-CIDR-Set-0.21/changes
release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2025-40911
related, third-party-advisory, us-government-resource
-
nvd.nist.gov
/vuln/detail/CVE-2026-45191
related, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2026-49942
- NVD CVE-2026-49942
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.