On this page (7 sections)
On 16 November 2026 Ubuntu published USN-8997-2, a security notice for a Net-SNMP vulnerability. It is the follow-up to USN-8997-1 and carries the same fix to Ubuntu 20.04 LTS, 18.04 LTS, 16.04 LTS and 14.04 LTS. According to Ubuntu, an unauthenticated remote attacker could possibly cause Net-SNMP to block indefinitely, which results in a denial of service.
If you run servers, network appliances built on Ubuntu, or monitoring setups that use the SNMP daemon (snmpd), this is worth a quick check. The fixed packages for these older releases are delivered through Ubuntu Pro, so the update path differs from a plain apt upgrade on a free install.
What happened
Ubuntu originally fixed this issue in USN-8997-1. USN-8997-2 is the companion notice that provides the corresponding fix for four older long-term support releases. The notice describes the original finding this way: Net-SNMP incorrectly handled newly accepted connections in the SMUX module, and an unauthenticated remote attacker could possibly use that to make Net-SNMP block indefinitely.
The notice lists the CVE identifier CVE-2026-89147 in its references. The research for this story contains no separate CVE record, so there is no CVSS score, no weakness classification and no exploitation data to report. Only Ubuntu's notice covers this so far, and this article relies on it alone.
Technical details
SMUX is the SNMP multiplexing module, a way for other programs to attach to the SNMP agent over a connection. The flaw sits in how the agent handles a newly accepted connection in that module. Ubuntu says the result is that Net-SNMP can block indefinitely. In plain terms, the daemon stops serving requests instead of crashing, so monitoring queries to that host would hang or time out until the service is restarted.
Ubuntu uses the word "possibly" and does not publish further mechanics. This article does not speculate beyond that, and it does not describe how to trigger the condition.
Who is affected
The notice covers these packages and releases:
| Ubuntu release | Packages | Fixed version |
|---|---|---|
| 20.04 LTS (focal) | libsnmp35, snmp, snmpd | 5.8+dfsg-2ubuntu2.9+esm3 |
| 18.04 LTS (bionic) | python-netsnmp, snmp, snmpd | 5.7.3+dfsg-1.8ubuntu3.8+esm2 |
| 16.04 LTS (xenial) | libsnmp30, snmp, snmpd | 5.7.3+dfsg-1ubuntu4.6+esm3 (Legacy Support add-on) |
| 14.04 LTS (trusty) | libsnmp30, python-netsnmp, snmp, snmpd | 5.7.2~dfsg-8.1ubuntu3.3+esm5 (Legacy Support add-on) |
Realistic exposure depends on whether snmpd is installed, running, and reachable over the network. Hosts that only have the snmp command-line client installed are a different case from hosts running the snmpd service. The notice does not say whether the SMUX module must be explicitly enabled for the issue to apply, so treat any host running snmpd as potentially affected until patched.
How to check your exposure
This command lists the installed Net-SNMP packages and their versions on Ubuntu. Run it on each server and compare the version column with the table above; a version ending in the listed esm suffix or newer means the fix is installed.
dpkg -l | grep -E 'snmp'This checks whether the SNMP daemon is running as a service. An active state means the host is serving SNMP and should be prioritized.
systemctl status snmpdThis shows whether anything is listening on the standard SNMP UDP port 161, and on which addresses. A listener bound to a public address is a higher risk than one bound only to localhost or a management network.
sudo ss -lunp | grep ':161'What to do now
- Inventory every Ubuntu host that has snmpd installed, including old 14.04, 16.04 and 18.04 machines that are easy to forget.
- Compare installed versions with the fixed versions in the table above.
- Attach the machines to Ubuntu Pro (free for up to five machines, per Ubuntu) so the fixed packages are available for these releases.
- Apply the update, then restart snmpd and confirm it answers a normal query.
- If you cannot patch yet, restrict access to UDP 161 with a firewall so only your monitoring systems can reach it.
- Where SNMP is not needed, stop and disable the service rather than leaving it exposed.
- Plan an upgrade for hosts on 14.04 and 16.04, which depend on the Legacy Support add-on for fixes.
Ubuntu states that a standard system update will make the necessary changes. These commands refresh package lists and upgrade only the Net-SNMP packages on a host that has Ubuntu Pro enabled.
sudo apt update
sudo apt install --only-upgrade snmpd snmp
sudo systemctl restart snmpdAfter updating, re-run the dpkg command above and confirm the version matches or exceeds the fixed one for your release.
Detection and monitoring
A denial of service of this kind shows up as a monitoring blind spot: SNMP polls time out while the rest of the server looks healthy. Watch for hosts whose SNMP checks fail or hang while the system is otherwise up, and check whether snmpd stops answering until restarted. The notice does not describe log signatures, so do not rely on a specific log line.
Also review what is reachable from the internet. An external security scan or a regular monitoring setup can help you notice services that are exposed more widely than intended, though neither replaces patching. For background on why exposed management services matter, see website security for small business.
Timeline
- Earlier: Ubuntu published USN-8997-1 with the original fix (exact date not given in the research).
- 16 November 2026: Ubuntu published USN-8997-2, extending the fix to Ubuntu 20.04, 18.04, 16.04 and 14.04 LTS.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
