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.
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 01 May 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
Fri, 01 May 2026 12:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:o:freebsd:freebsd:13.5:-:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:beta3:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p10:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p11:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p12:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p1:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p2:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p3:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p4:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p5:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p6:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p7:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p8:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:13.5:p9:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:-:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p10:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p11:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p1:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p2:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p3:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p4:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p5:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p6:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p7:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p8:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.3:p9:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.4:-:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.4:p1:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.4:p2:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:14.4:rc1:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:15.0:-:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:15.0:p1:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:15.0:p2:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:15.0:p3:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:15.0:p4:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:15.0:p5:*:*:*:*:*:* cpe:2.3:o:freebsd:freebsd:15.0:p6:*:*:*:*:*:* |
Thu, 30 Apr 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Thu, 30 Apr 2026 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Freebsd
Freebsd freebsd |
|
| Vendors & Products |
Freebsd
Freebsd freebsd |
Thu, 30 Apr 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Heap overflow in libnv | |
| Weaknesses | CWE-122 CWE-130 |
|
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: freebsd
Published:
Updated: 2026-05-01T15:26:28.941Z
Reserved: 2026-04-28T15:08:10.642Z
Link: CVE-2026-35547
Updated: 2026-04-30T13:12:22.260Z
Status : Modified
Published: 2026-04-30T09:16:03.167
Modified: 2026-05-01T16:16:30.273
Link: CVE-2026-35547
No data.
OpenCVE Enrichment
Updated: 2026-05-02T00:30:16Z