# CVE-2026-39006: SNMP4J-Agent allows a remote attacker to execute arbitrary code via the snmp4jCfgStoragePath component

> Remote attackers can execute arbitrary code in SNMP4J-Agent via unsafe deserialization in the configuration storage path.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-7h7j-7vwp-cwfg

## What is CVE-2026-39006?

CVE-2026-39006 is a critical unsafe deserialization vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in SNMP4J-Agent 3.8.3 allows a remote attacker to execute arbitrary code via the snmp4jCfgStoragePath component.

Weakness: CWE-73 (External Control of File Name or Path), CWE-502 (Deserialization of Untrusted Data), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-39006?

2 open source packages ship an affected version, including org.snmp4j:snmp4j-agent.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.snmp4j:snmp4j-agent` | Maven | All versions to 3.8.3 | None |
| `org.snmp4j:snmp4j-agent` | Maven | All versions to 3.8.3 | None |

## How do I fix CVE-2026-39006?

No fix has been published for CVE-2026-39006 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-39006 being exploited?

There is no known exploitation of CVE-2026-39006 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39006 and fix it if it is affected.

What it is: CVE-2026-39006 is a critical unsafe deserialization vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-39006 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.snmp4j:snmp4j-agent (Maven): affected all versions up to 3.8.3; no fix listed
- org.snmp4j:snmp4j-agent (Maven): affected all versions up to 3.8.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-39006/ (Markdown: https://insights.sbomify.com/CVE-2026-39006/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-39006
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-39006
- OSV: https://osv.dev/vulnerability/CVE-2026-39006

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-39006/
Summaries are generated and may contain mistakes; the official description above is the record.