Junos OS Evolved EUVD-2026-101456

Exploitation requires network reachability to the specific TCP/UDP port on which the affected internal process was inadvertently bound due to faulty initialization; the description states the process 'should only be able to communicate internally within the device' but can be 'reached over the network via an open port.' No authentication is required (PR:N) and no user interaction is needed (UI:N), so any attacker with routed access to that port on an unpatched device can trigger it against default-installed firmware. The primary limiting factor is network exposure: devices where the relevant interface/port is firewalled, restricted to management/internal networks, or otherwise unreachable are not practically exploitable. Impact is inherently bounded - limited information disclosure and increased CPU load, not device compromise. Affected builds: all Junos OS Evolved before 23.2R2-S7.7-EVO, 23.4 before 23.4R2-S8.11-EVO, 24.2 before 24.2R2-S5.6-EVO, 24.4 before 24.4R2-S4-EVO, 25.2 before 25.2R2-S1-EVO, and 25.4 before 25.4R1-S1-EVO.

This is a moderate-severity (CVSS 6.5) issue whose signals are internally consistent but point to limited impact. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L indicates a network-reachable, low-complexity, unauthenticated flaw, matching the description of an internal-only process inadvertently exposed on an open port. However, both the confidentiality and availability impacts are rated LOW (C:L/A:L) and there is NO integrity impact (I:N), so this is a limited information-disclosure plus resource-consumption (elevated CPU) issue rather than a device-takeover or full-DoS vulnerability. No EPSS score, KEV listing, or POC was provided in the input; exploitation status is therefore 'no public exploit identified at time of analysis.' There is no SSVC decision data supplied. Net assessment: a legitimate network-exposed defect worth patching during normal maintenance cycles, but NOT an emergency - it is a moderate-CVSS issue with correspondingly moderate real-world risk, absent any evidence of active exploitation or automatability. One caveat to verify with the vendor: the Juniper advisory (JSA112171) was not retrievable in this analysis, so the exact affected platforms (which Junos OS Evolved hardware families), the specific exposed process, and the open port number are not independently confirmed.

A network-positioned attacker who can reach an affected Junos OS Evolved device sends packets to a TCP/UDP port that should have been bound only to the device's internal communication domain. Because of the faulty initialization, an internal process receives and processes these ingress packets, leaking limited internal information and consuming additional CPU cycles. No public exploit code was identified at the time of analysis, and because privileges are not required (PR:N) with low attack complexity (AC:L), exploitation is technically straightforward for anyone with network reachability to the exposed port.