CVE-2026-49941
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNet::CIDR::Set versions through 0.20 for Perl did not validate IP addresses. The add method called the _encode method to parse addresses. If the addresses did not look like netmasks or network ranges, then they were assumed to single IP addresses and passed back to itself as a 32-bit or 128-bit netmask. If the argument was not a well-formed IP address, then this would lead to indefinite recursion. An attacker could use this to cause a denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Net::CIDR::Set Perl module (versions through 0.20) fails to validate IP addresses in the add method. When addresses don't match netmask or network range format, they're treated as single IPs and passed as 32/128-bit netmasks back to the add method, causing infinite recursion with malformed input leading to denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.21CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Net::CIDR::Set is installedRun `perl -MNet::CIDR::Set -e 'print "Installed\n"'` to verify the module exists on the systemAffected if The module is not installed or the command fails
-
Determine the installed version of Net::CIDR::SetRun `perl -MNet::CIDR::Set -e 'print $Net::CIDR::Set::VERSION'` to obtain the version numberAffected if The version is 0.20 or lower (any version through 0.20 is affected)
-
Check for Perl scripts using the add() methodSearch source code for patterns like `->add(` or `add(` where Net::CIDR::Set objects are used, such as `grep -r '->add(' /path/to/code`Affected if Code calls the add() method on Net::CIDR::Set objects
-
Inspect input sources to add() methodReview code paths where data flows into add() calls; check if input comes from user input, external files, APIs, or network sources without prior validationAffected if Untrusted or unsanitized input can reach the add() method, enabling malicious crafted input to trigger infinite recursion
You are affected if Net::CIDR::Set version 0.20 or lower is installed AND your code uses the add() method with input that could be malformed or from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.21
Update to a patched version of Net::CIDR::Set when available; until then, implement input validation sanitization before calling add() to reject malformed IP strings.
Net::CIDR::Set version 0.21
- Upgrade Net::CIDR::Set to version 0.21 or later using your Perl module management tool (e.g., 'cpan Net::CIDR::Set' or 'cpanm Net::CIDR::Set')
- Verify the installed version using 'perl -MNet::CIDR::Set -e "print $Net::CIDR::Set::VERSION"'
- Ensure the version is 0.21 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49941 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data