# CVE-2026-48694: Command injection in n/a

> Attackers can inject arbitrary NETCONF commands via unsanitized IP input in the Juniper plugin, leading to full router compromise.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 26 May 2026
- **Also known as:** DEBIAN-CVE-2026-48694, GHSA-f98m-cp3g-ghc5, UBUNTU-CVE-2026-48694

## What is CVE-2026-48694?

CVE-2026-48694 is a high-severity command injection vulnerability in n/a, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FastNetMon Community Edition through 1.2.9 contains a configuration injection vulnerability in the Juniper router integration plugin. In src/juniper_plugin/fastnetmon_juniper.php, the $IP_ATTACK variable (received from argv[1]) is directly interpolated into Juniper NETCONF set-configuration commands at lines 69 and 90 without any validation or sanitization. Line 69: $conn->load_set_configuration("set routing-options static route {$IP_ATTACK} community 65535:666 discard"). Line 90: $conn->load_set_configuration("delete routing-options static route {$IP_ATTACK}/32"). An attacker who can control the IP address string can inject additional Juniper CLI configuration commands by embedding newline characters followed by arbitrary set/delete commands. This could modify the router's routing table, firewall filters, user accounts, or any other configuration element accessible via NETCONF. The impact is full router compromise.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Pavel-Odintsov Fastnetmon.

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

Apply the vendor's patch.

## Is CVE-2026-48694 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-48686](https://insights.sbomify.com/CVE-2026-48686/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-48689](https://insights.sbomify.com/CVE-2026-48689/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-48687](https://insights.sbomify.com/CVE-2026-48687/): Command injection in n/a (high 8.1)
- [CVE-2026-48692](https://insights.sbomify.com/CVE-2026-48692/): Missing authorization in n/a (high 8.1)
- [CVE-2026-48695](https://insights.sbomify.com/CVE-2026-48695/): Command injection in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48694 is a high-severity command injection vulnerability in n/a, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48694 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-48694/ (Markdown: https://insights.sbomify.com/CVE-2026-48694/index.md)
```

## Sources

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

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