dbcve.org
JunosOperating system · Juniper

CVE-2026-57032

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 23.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper handling of undefined parameters in the packet forwarding engine (pfe) of Juniper Networks Junos OS on EX Series allows an authenticated low-privilege attacker to cause FPC crashes by subscribing to unsupported telemetry sensor paths via gRPC, leading to complete service outage until automatic restart.

MitigationUpgrade Junos OS to fixed versions (23.2R2-S7, 23.4R2-S8, 24.2R2-S5, 24.4R2 or later); until then, restrict gRPC access to trusted users and monitor for AGENTD_RESOURCE_NOT_FOUND log messages.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:< 23.2= 23.2= 23.4= 24.2= 24.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Junos OS version
    Run 'show version' command on the device CLI to obtain the installed Junos OS version
    Affected if Version is before 23.2, or is in the 23.2, 23.4, 24.2, or 24.4 release families (and not at fixed sub-versions)
  2. Confirm gRPC service is enabled
    Run 'show configuration system services grpc' to check if gRPC service is configured and active
    Affected if gRPC is enabled and accessible to the attacker (authenticated low-privilege user)
  3. Check for AGENTD_RESOURCE_NOT_FOUND log messages
    Run 'show log messages | match AGENTD_RESOURCE_NOT_FOUND' or review system logs for these specific messages
    Affected if Log messages contain AGENTD_RESOURCE_NOT_FOUND entries indicating exploitation attempts
  4. Verify FPC status for crashes
    Run 'show chassis fpc' to check for any FPCs that are offline or have crashed
    Affected if Any FPC shows as offline or crashed, especially following gRPC sensor subscription activity

User is affected if Junos OS version matches the affected releases, gRPC is enabled, and exploitation via gRPC sensor subscription has occurred leading to FPC crashes or AGENTD_RESOURCE_NOT_FOUND logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 23.2 or later
Fixed in 23.2
Interim mitigation

Upgrade Junos OS to fixed versions (23.2R2-S7, 23.4R2-S8, 24.2R2-S5, 24.4R2 or later); until then, restrict gRPC access to trusted users and monitor for AGENTD_RESOURCE_NOT_FOUND log messages.

Recommended fix High confidence

23.2R2-S7 or later (23.2 branch), 23.4R2-S8 or later (23.4 branch), 24.2R2-S5 or later (24.2 branch), or 24.4R2 or later (24.4 branch)

  1. 1. Identify the current Junos OS version running on the EX Series device (EX2300, EX3400, EX4000, EX4100, or EX4400) using 'show version' command.
  2. 2. Determine which upgrade path applies based on current version branch (23.2, 23.4, 24.2, or 24.4).
  3. 3. For devices on 23.2 branch: upgrade to 23.2R2-S7 or later.
  4. 4. For devices on 23.4 branch: upgrade to 23.4R2-S8 or later.
  5. 5. For devices on 24.2 branch: upgrade to 24.2R2-S5 or later.
  6. 6. For devices on 24.4 branch: upgrade to 24.4R2 or later.
  7. 7. For devices on versions before 23.2: upgrade to 23.2R2-S7 or later.
  8. 8. Before upgrading, review Juniper release notes for any compatibility notes or prerequisites.
Caveat Upgrading across major branches may introduce compatibility changes; review release notes for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57032 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57032 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data