Cyber Resilience

CVE-2026-40199

Stigtsp Net\ \

Published
10 April 2026
Modified
21 April 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0031 23th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-40199 is a medium-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Stigtsp Net\. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and SC-7 (Boundary Protection) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Net::CIDR::Lite versions before 0.23 for Perl mishandles IPv4 mapped IPv6 addresses, which may allow IP ACL bypass. _pack_ipv6() includes the sentinel byte from _pack_ipv4() when building the packed representation of IPv4 mapped addresses like ::ffff:192.168.1.1. This produces an 18 byte…

more

value instead of 17 bytes, misaligning the IPv4 part of the address. The wrong length causes incorrect results in mask operations (bitwise AND truncates to the shorter operand) and in find() / bin_find() which use Perl string comparison (lt/gt). This can cause find() to incorrectly match or miss addresses. Example: my $cidr = Net::CIDR::Lite->new("::ffff:192.168.1.0/120"); $cidr->find("::ffff:192.168.2.0"); # incorrectly returns true This is triggered by valid RFC 4291 IPv4 mapped addresses (::ffff:x.x.x.x). See also CVE-2026-40198, a related issue in the same function affecting malformed IPv6 addresses.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Why these techniques?

Logic error in IPv4-mapped IPv6 handling produces incorrect CIDR matches, enabling direct bypass of IP ACLs in any public-facing service that uses the library for access control.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-40198Same product: Stigtsp Net\
CVE-2026-33555Shared CWE-130
CVE-2026-47692Shared CWE-130
CVE-2025-14847Shared CWE-130
CVE-2026-26081Shared CWE-130
CVE-2026-54466Shared CWE-130
CVE-2026-5367Shared CWE-130
CVE-2025-8531Shared CWE-130
CVE-2026-3868Shared CWE-130
CVE-2026-33846Shared CWE-130

Affected Assets

stigtsp
net\
\

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • SI-10 Information Input Validation
  • SC-7 Boundary Protection
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.5.5
  • V4.2.1
  • V4.2.2

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires timely patching or updating of the vulnerable Net::CIDR::Lite library to version 0.23+ that corrects the _pack_ipv6 length error for IPv4-mapped addresses.

prevent

Requires validation of IP address inputs to reject or normalize IPv4-mapped IPv6 forms (::ffff:x.x.x.x) before they reach the flawed pack/find routines.

prevent

Enforces boundary access control lists using vetted mechanisms rather than the defective Perl module, preventing the ACL bypass condition.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce length validation and input sanitization during coding and review.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing in development can detect length-inconsistency vulnerabilities before deployment.

prevents

Secure development lifecycle mandates input validation and length checks that directly address inconsistent length fields.

prevents

Application security requirements include explicit rules for handling message lengths and data structures.

prevents

Secure architecture principles require robust parsing and bounds checking to prevent length-related flaws.

prevents

Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.

References