CVE-2026-63201

7.1High

Published 30 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite

7.1CVSS

High

0CVSS v4.010

Attack vector
Network
Complexity
Low
Privileges
Low
User action
None
Impact
High impact on availability
Weakness
CWE-134

What an attacker gets

Authenticated NETCONF users can crash the netopeer2-server by sending a malformed subtree filter. This results in a denial of service for network configuration management.

Root cause

The application passes a user-controlled buffer as a format string to vsyslog in the logging module.

Affected versions

  • Netopeer2 version 2.8.7 is confirmed affected
  • the fix is verified in 2.8.21

CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade to Netopeer2 version 2.8.21 or later. If you cannot upgrade, restrict NETCONF access to trusted users only.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

Netopeer2 is a server for implementing network configuration management based on the `NETCONF` Protocol. In affected versions, a low-privileged authenticated `NETCONF` user can remotely crash `netopeer2-server` by sending a `get RPC` with an invalid `subtree filter` whose text contains format specifiers. In `src/netconf.c`, `np2srv_rpc_get_cb()` sends the invalid value through `ERR()` to `np2log_printf()`, where `vsnprintf()` first formats the message safely. In `src/log.c`, that already formatted buffer is subsequently passed to `np2log()` as the format string itself, causing `vsyslog()` to interpret attacker-controlled percent sequences and read invalid pointer arguments. The reported denial of service was confirmed on version 2.8.7 using `NETCONF`-over-SSH and AddressSanitizer; reliable remote code execution was not confirmed. `The advisory identifies 2.8.8 as patched`; repository comparisons verify the fix in public release 2.8.21. The affected/fixed boundary remains unresolved because no public 2.8.8 tag was located, which does not establish the status of an untagged 2.8.8 build.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-63201