# CVE-2026-57032: Junos OS: EX Series: Subscribing to an unsupported telemetry sensor path causes fxpc process crash

> Authenticated low-privilege attackers can crash the forwarding engine by subscribing to unsupported telemetry paths, causing service outages on Juniper EX switches.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-hp6x-whrh-rg9m

## What is CVE-2026-57032?

CVE-2026-57032 is a high-severity denial of service vulnerability in Juniper Junos, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Improper Handling of Undefined Parameters vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on EX Series devices allows an authenticated attacker with low privileges to cause a Denial-of-Service (DoS).

If an attempt is made to subscribe to an unsupported telemetry sensor path on EX2300, EX3400, EX4000, EX4100 and EX4400 via gRPC, this causes the FPC to crash. This leads to a complete service outage until the module has automatically restarted. 

The following log message can be seen when this issue happens:

agentd[<PID>]: AGENTD_RESOURCE_NOT_FOUND: No resource name found for <sensor>

This issue affects Junos OS on 

EX2300, EX3400, EX4000, EX4100 and EX4400

devices:

  *  all versions before 23.2R2-S7,
  *  23.4 versions before 23.4R2-S8,
  *  24.2 versions before  24.2R2-S5,
  *  24.4 versions before 24.4R2.

Weakness: CWE-236 (Improper Handling of Undefined Parameters)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2026-57032 being exploited?

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

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57032 is a high-severity denial of service vulnerability in Juniper Junos, published on 9 Jul 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-57032 in the wild and no public exploit code.

Affected product: Juniper Junos. 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-57032/ (Markdown: https://insights.sbomify.com/CVE-2026-57032/index.md)
```

## Sources

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

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