When exchanging data over a socket, libnv uses select(2) to wait for data to arrive. However, it does not verify whether the provided socket descriptor fits in select(2)'s file descriptor set size limit of FD_SETSIZE (1024). An attacker who is able to force a libnv application to allocate large file descriptors, e.g., by opening many descriptors and executing a program which is not careful to close them upon startup, can trigger stack corruption. If the target application is setuid-root, then this could be used to elevate local privileges.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.8, requiring local system access to exploit with relatively low complexity without requiring user interaction requiring only low-level privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from freebsd organizations running these solutions should prioritize assessment and patching.
Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2026-04-30T09:16:03.270
2026-05-01T12:41:46.590
Analyzed
CVSSv3.1: 7.8 (HIGH)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 13.5 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.3 | Yes |
| Operating System | freebsd | freebsd | 14.4 | Yes |
| Operating System | freebsd | freebsd | 14.4 | Yes |
| Operating System | freebsd | freebsd | 14.4 | Yes |
| Operating System | freebsd | freebsd | 14.4 | Yes |
| Operating System | freebsd | freebsd | 15.0 | Yes |
| Operating System | freebsd | freebsd | 15.0 | Yes |
| Operating System | freebsd | freebsd | 15.0 | Yes |
| Operating System | freebsd | freebsd | 15.0 | Yes |
| Operating System | freebsd | freebsd | 15.0 | Yes |
| Operating System | freebsd | freebsd | 15.0 | Yes |
| Operating System | freebsd | freebsd | 15.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For freebsd's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.