Findings

CVE-2026-35547

When processing the header of an incoming message, libnv failed to properly validate the message size.

Published Apr 30, 2026 · updated Jun 17, 2026 · freebsd freebsd

When processing the header of an incoming message, libnv failed to properly validate the message size. The lack of validation allows a malicious program to write outside the bounds of a heap allocation. This can trigger a crash or system panic, and it may be possible for an unprivileged user to exploit the bug to elevate their privileges.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 30, 2026 · NIST NVD

    Detected

    When processing the header of an incoming message, libnv failed to properly validate the message size. The lack of validation allows a malicious program to write outside the bounds of a heap allocation. This can trigger a crash or system panic, and it may be possible for an unprivileged user to exploit the bug to elevate their privileges.

  2. Jun 17, 2026 · NIST NVD

    Updated

    When processing the header of an incoming message, libnv failed to properly validate the message size. The lack of validation allows a malicious program to write outside the bounds of a heap allocation. This can trigger a crash or system panic, and it may be possible for an unprivileged user to exploit the bug to elevate their privileges.

Affected

  • cpe freebsd/freebsd13.5

Sources

  • CVE.orgVulnerability recordCVE-2026-35547

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-35547

    When processing the header of an incoming message, libnv failed to properly validate the message size. The lack of validation allows a malicious program to write outside the bounds of a heap allocation. This can trigger a crash or system panic, and it may be possible for an unp

    nvd.nist.gov

References