Executive Summary

CVE-2026-39006 is a remote code execution vulnerability found in SNMP4J-Agent version 3.8.3. It involves the snmp4jCfgStoragePath component, where a remote attacker can exploit the default configuration to modify the storage path and trigger store or restore operations.

By using the default community string "public," an attacker can set a path they control, which leads to the DefaultMOPersistenceProvider using Java object deserialization via ObjectInputStream. This process can be exploited to execute arbitrary code depending on deployment and classpath conditions.

The vulnerability also allows file write or overwrite operations through the store function and can cause denial of service during deserialization of invalid input.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can allow a remote attacker to execute arbitrary code on the affected system, potentially taking full control depending on the environment.

It also enables attackers to write or overwrite files on the system, which can lead to data corruption or unauthorized data modification.

Additionally, the vulnerability can cause denial of service by triggering failures during deserialization of invalid input, potentially disrupting service availability.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by checking if SNMP4J-Agent version 3.8.3 is in use and if the default community string "public" is enabled, which allows remote attackers to exploit the snmp4jCfgStoragePath component.

Detection can involve monitoring SNMP traffic for requests using the "public" community string and attempts to modify the storage path or trigger store/restore operations.

Suggested commands include using snmpwalk or snmpget to query SNMP agents with the community string "public" to identify vulnerable configurations.

• snmpwalk -v2c -c public <target-ip> .
• snmpget -v2c -c public <target-ip> <OID>

Additionally, reviewing logs for file creation or deserialization errors related to SNMP4J-Agent may help detect exploitation attempts.

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include removing default write privileges from the SNMP4J-Agent configuration to prevent unauthorized modification of the storage path.

Restrict the storage paths to safe directories to avoid arbitrary file writes or overwrites.

Replace Java deserialization mechanisms with safer formats to prevent arbitrary code execution.

Enable source address filtering for SNMPv1/v2c to limit access to trusted hosts only.

Useful 0 Not Useful 0