Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege management access
-
DeliveryReach gRPC/gNMI telemetry service
-
ExploitSubscribe to unsupported pfe sensor path
-
ExecutionTrigger undefined-parameter fault in agentd
-
PersistCrash FPC and drop forwarding
-
ImpactRepeat to sustain outage
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Exploitation requires that the target be an EX2300, EX3400, EX4000, EX4100 or EX4400 running an affected Junos OS release with the Junos Telemetry Interface / gRPC (gNMI) streaming service reachable, and the attacker must hold a low-privilege authenticated account able to open a gRPC telemetry subscription (CVSS PR:L confirms authentication is needed; not exploitable unauthenticated). The concrete trigger is subscribing to an UNSUPPORTED telemetry sensor path on the pfe - a supported path does not cause the crash. Limiting factors that reduce real-world risk: the gRPC telemetry interface is commonly confined to a management VLAN or specific collector hosts, so an attacker needs network reach to that plane plus valid credentials; the impact is availability-only and self-recovers (R:A) after the FPC restarts, so a single request causes a transient rather than permanent outage; and only the five listed EX models are affected. |
| Impact | The CVSS 4.0 base score is 7.1 (High) with vector AV:N/AC:L/AT:N/PR:L/UI:N and impact confined to availability (VA:H, SA:L; VC:N/VI:N). This is a genuine availability risk but strictly a DoS - no confidentiality or integrity exposure and no code execution. Positive risk signals: network reachable, low attack complexity, no user interaction, and only low privileges needed, so any authenticated management-plane user or a compromised low-tier account can trigger it. Mitigating signals: exploitation requires authenticated gRPC access to the telemetry interface, which in well-run networks is restricted to a management VLAN or NOC/monitoring systems; no EPSS score was provided, and there is no POC or KEV listing, so there is no evidence of active or opportunistic exploitation. The vector's R:A (automatic recovery) reflects that the FPC self-restarts, limiting damage to a transient outage per trigger - though an attacker scripting repeated subscriptions can sustain the outage. Net: a real patch-worthy priority for EX fleets exposing gRPC telemetry, but lower urgency than an unauthenticated or RCE bug; prioritize by whether telemetry is reachable from untrusted accounts. |
| Exploit ScenarioDerived | An attacker holding a low-privilege authenticated foothold on the switch's management plane - or on a monitoring host permitted to reach the gRPC endpoint - opens a telemetry subscription to a sensor path that the EX platform does not support. The malformed/undefined path resolution crashes the FPC and drops the switch's forwarding for the duration of the auto-restart, and the attacker scripts repeated subscriptions to keep the device offline. No public exploit code has been identified, but the low complexity (AC:L, no user interaction) makes reproduction trivial for anyone with the required access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 09, 2026
Denial-of-service in Juniper Networks Junos OS on EX Series switches (EX2300, EX3400, EX4000, EX4100, EX4400) lets a low-privileged authenticated attacker crash the Flexible PIC Concentrator (FPC) by subscribing over gRPC to an unsupported telemetry sensor path in the packet forwarding engine. Each crash produces a complete forwarding outage until the module auto-restarts, and the trigger can be repeated for sustained disruption. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the low complexity and single low-privilege prerequisite make it operationally easy to trigger.
RemediationAI
Vendor-released patch: upgrade Junos OS to a fixed release for the affected EX Series switches - 23.2R2-S7 or later, 23.4R2-S8 or later, 24.2R2-S5 or later, or 24.4R2 or later (per Juniper advisory JSA110092, https://supportportal.juniper.net/JSA110092). Until patching is possible, reduce exposure by restricting who can open gRPC telemetry subscriptions: limit management/telemetry-plane access to trusted collector hosts using firewall filters (loopback/lo0 filters) and management-interface ACLs so only authorized JTI collectors can reach the gRPC service, and tighten authorization so low-privilege accounts cannot establish telemetry subscriptions. If Junos Telemetry Interface / gRPC streaming is not in use, disabling the telemetry (gRPC/gNMI) service removes the attack surface entirely; the trade-off is loss of streaming telemetry to monitoring platforms, so coordinate with the NOC before disabling. These controls limit but do not eliminate risk from a trusted-but-compromised collector, so treat them as interim measures pending the upgrade.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw lives in Junos OS's Junos Telemetry Interface (JTI) streaming path, where the agentd process brokers gRPC/gNMI telemetry subscriptions to sensor paths served by the packet forwarding engine (pfe) on EX Series switches. CWE-236 (Improper Handling of Undefined Parameters) captures the root cause: when a client requests a sensor path the platform does not implement, the code fails to gracefully reject the undefined parameter and instead drives the FPC into a crash rather than returning a clean error. The diagnostic signature 'AGENTD_RESOURCE_NOT_FOUND: No resource name found for <sensor>' confirms the request reaches resource resolution before the fault. The CPE cpe:2.3:a:juniper_networks:junos_os:*:*:*:*:*:*:*:* identifies Junos OS as the affected software, though the defect is realized only on the listed fixed-config EX switch models whose FPC runs the vulnerable pfe telemetry handler.
Know when Junos Os gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Network-reachable gRPC telemetry with only a low-privilege account (PR:L) and no user interaction crashes the FPC for availability-only impact (A:H); no confidentiality or integrity effect.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
3DescriptionCVE.org
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.
Articles & Coverage 2
Executive ViewAI
Juniper Networks Junos OS on EX Series switches (EX2300, EX3400, EX4000, EX4100, EX4400) contains a denial-of-service vulnerability allowing low-privileged authenticated users to repeatedly crash the packet forwarding engine, causing complete network outage until module auto-restart. The attack requires minimal technical complexity and can sustain disruption indefinitely, creating critical availability risk for organizations relying on these switches for core infrastructure. No vendor patch exists, requiring immediate implementation of access controls and enhanced monitoring.
No vendor-released patch identified at time of analysis. Interim mitigations required: (1) Restrict gRPC telemetry access exclusively to authorized management subnets via firewall ACLs; (2) Disable all non-critical telemetry sensor subscriptions to reduce attack surface; (3) Implement detailed logging and alerting on gRPC connection attempts and FPC restart sequences to detect repeated exploitation; (4) Apply network segmentation to limit low-privilege user access to affected switches; (5) Maintain spare FPC modules and documented restart procedures for rapid incident response; (6) Conduct quarterly access reviews to identify and revoke unnecessary authenticated credentials.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
OS command injection in the phcd phone-home daemon of Juniper Networks Junos OS and Junos OS Evolved lets an adjacent, u
Unauthenticated remote code execution with root privileges affects Juniper Networks Junos OS devices that expose the J-W
Heap-based buffer overflow in the sdxd service-deployment daemon of Juniper Networks Junos OS and Junos OS Evolved allow
A stack-based buffer overflow in the srxpfe packet forwarding process of Juniper Networks Junos OS on SRX Series devices
Unauthenticated remote code execution with elevated privileges is possible in Juniper Junos OS and Junos OS Evolved thro
Remote root code execution in the routing protocol daemon (rpd) of Juniper Junos OS is reachable through protocol-valid
Remote code execution (on Junos OS) and rpd denial of service (on Junos OS and Junos OS Evolved) result from a stack-bas
Remote code execution with root privileges on Juniper Networks Junos OS and Junos OS Evolved is possible when the routin
Remote code execution and denial of service in Juniper Networks Junos OS and Junos OS Evolved arise from a stack-based b
Unauthenticated remote attackers can gain root-level configuration access and fully compromise Juniper Junos OS and Juno
Integer underflow in the Junos OS kernel can crash a device when the Extended Echo feature (RFC 8335 ICMP probing) is co
Heap-based buffer overflow in Juniper Networks Junos OS on SRX Series devices that have Secure Vector Routing (SVR) enab
EUVD-2026-42723
GHSA-hp6x-whrh-rg9m
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB