OSV-2025-161
Heap-buffer-overflow in se_add_pair
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=398356443
Crash type: Heap-buffer-overflow READ 8
Crash state:
se_add_pair
se_read_conf
run_config_handler
What each source reports
OSV No score
Heap-buffer-overflow in se_add_pair
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=398356443
Crash type: Heap-buffer-overflow READ 8
Crash state:
se_add_pair
se_read_conf
run_config_handler
- Record
OSV-2025-161- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
net-snmpOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2025-161 is a vulnerability with no CVSS score yet in net-snmp, published February 24, 2025. No source lists public exploit code. A source reports a fix.