Cyber Resilience

CVE-2026-57032

Juniper Junos ≤ 23.2

Published
09 July 2026
Modified
13 July 2026
Patch / advisory
View advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:A/V:X/RE:M/U:X
EPSS Score 0.0042 35th percentile
Risk Priority 36 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-57032 is a high-severity Improper Handling of Undefined Parameters (CWE-236) vulnerability in Juniper Junos. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-236

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-33802Same product: Juniper Ex2300
CVE-2026-57027Same product: Juniper Ex4100
CVE-2023-28961Same product: Juniper Junos
CVE-2025-30644Same product: Juniper Ex2300
CVE-2026-57025Same product: Juniper Ex2300
CVE-2025-52949Same product: Juniper Junos
CVE-2023-28964Same product: Juniper Junos
CVE-2023-44203Same product: Juniper Ex2300
CVE-2024-39565Same product: Juniper Ex2300
CVE-2025-30659Same product: Juniper Junos

Affected Assets

juniper
junos
23.2, 23.4, 24.2, 24.4 · ≤ 23.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly enforces checking and handling of all supplied parameters, preventing acceptance of undefined names.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles applied during design and development include explicit rules for rejecting or safely ignoring undefined parameters.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require robust input validation and parameter handling to prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect undefined-parameter handling flaws but does not prevent them at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires explicit definition and validation of all parameters, reducing undefined-parameter handling issues.

A.8.26 Application security requirements partial match
prevents

Application security requirements mandate complete parameter specifications and error handling for unsupported inputs.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper handling of undefined or unsupported parameters during implementation.

References