CVE-2026-59961: troglobit mini-snmpd · Out-of-bounds Read
Affects troglobit mini-snmpdSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 1.7 soon.
Data as of 18 Nov 2026, 21:38 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.2 |
|---|
- Patch
- Available – fixed in 1.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade mini-snmpd and troglobit/mini-snmpd to 1.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| troglobitmini-snmpd | Affected
| Fixed in
|
GitHubtroglobit/mini-snmpdpkg:github/troglobit/mini-snmpdOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade mini-snmpd to version 1.7 or later, where this vulnerability is fixed. No other mitigation is indicated or required as the fix addresses the root cause.
Description
CVE-2026-59961 is a high-severity out-of-bounds read vulnerability in the ASN.1 BER parser of troglobit mini-snmpd versions prior to 1.7. The flaw arises because the parser does not properly verify that an attacker-controlled field length is within the remaining packet size, leading to unsigned integer wraparound and out-of-bounds memory reads. This can be triggered remotely by an unauthenticated attacker sending a crafted request to UDP port 161, potentially causing a crash and disclosure of adjacent heap memory. The issue is fixed in version 1.7.