Junos OS Evolved
CVE-2025-52961
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain foothold on adjacent L2 device
-
DeliverySend crafted valid CFM packets to router
-
ExploitSpike cfmd CPU and leak cfmman memory
-
ExecutionExhaust FPC memory causing crash/restart
-
ImpactSustain packet flow to maintain DoS
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that Connectivity Fault Management (CFM / 802.1ag) be configured and active on the device, and that the attacker occupy an adjacent position on a directly connected L2 segment (AV:A) from which the specific valid CFM packets can reach cfmd. Limiting factors: only Junos OS Evolved on PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008, and PTX10016 running affected trains (from 23.2R1-EVO through the listed fixed versions) is vulnerable; releases before 23.2R1-EVO are not affected; no authentication or user interaction is needed (PR:N/UI:N), but the adjacency requirement means purely remote internet-based exploitation is not possible. |
| Impact | This is a genuine but moderate-priority operational availability issue rather than a critical emergency. The CVSS 4.0 vector (AV:A/AC:L/PR:N/UI:N) confirms an adjacent, unauthenticated, low-complexity attack, but the impact is availability-only (VC:N/VI:N/VA:H, SA:L) - there is no confidentiality or integrity exposure. Signals are largely consistent: the adjacency requirement (AV:A) means an attacker must already be on a directly connected L2 segment, which meaningfully narrows the threat to a position inside the network rather than the open internet. EPSS is low at 0.48% (40th percentile), which aligns with the adjacency constraint and the narrow affected-device scope and argues against mass, opportunistic exploitation. A public exploit is reported to exist (POC=YES) but there is no CISA KEV listing, so there is no evidence of active exploitation - POC availability and active exploitation are distinct and should not be conflated. The one point worth verifying is the AU:Y (automatable) and V:C (concentrated value) supplemental metrics combined with a public POC: an on-path attacker could sustain the DoS cheaply, so for operators of the specific affected PTX10000-series routers this warrants prompt patching despite the modest 7.1 score. Net: real but position-gated availability risk, not a high-CVSS-but-illusory issue. |
| Exploit ScenarioDerived | An attacker who has gained a foothold on a device directly adjacent to an affected PTX10000-series router (e.g., a compromised neighbor on the same L2 link where CFM is active) sends a stream of specific but otherwise valid CFM packets. This drives the cfmd process to 100% CPU and leaks cfmman memory until the FPC (line card) crashes and restarts; continued packet delivery sustains the outage. A public exploit is reported to exist, and the low attack complexity (AC:L) means no special timing or race is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
An unauthenticated attacker on an adjacent Layer 2 segment can sustain a denial-of-service condition against Juniper Junos OS Evolved on the PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008 and PTX10016 platforms by sending specific valid Connectivity Fault Management (CFM / 802.1ag) packets, which drive the cfmd daemon to 100% CPU and cause the cfmman process to leak memory until the FPC crashes and restarts. Only devices running the affected release trains (23.2R1-EVO onward) with CFM configured and active are vulnerable; releases before 23.2R1-EVO are not affected, and the AV:A requirement means purely internet-based remote exploitation is not possible. Publicly available exploit code exists, the EPSS score is low (0.48%, roughly the 40th percentile), and this issue is assessed as a genuine but moderate-priority operational availability problem rather than a critical emergency.
RemediationAI
Juniper has released fixed software, so upgrade to the version that corresponds to the deployed train: 23.2R2-S4-EVO for 23.2, 23.4R2-S4-EVO for 23.4, 24.2R2-EVO for 24.2, and 24.4R1-S2-EVO or 24.4R2-EVO for 24.4; installations older than 23.2R1-EVO are not affected and need no action. Where the upgrade cannot be scheduled immediately, the most effective compensating control is to disable Connectivity Fault Management (802.1ag) on the affected PTX platforms if the OAM feature is not operationally required - the trade-off is loss of CFM continuity checking, loopback/linktrace diagnostics and fault isolation for the impacted L2 services. If CFM must remain enabled, restrict the L2 adjacency so that only trusted, directly connected devices can inject CFM frames: apply port-level filters or firewall terms matching CFM Ethertype 0x8902 to drop CFM frames from untrusted access ports, or use MAC limiting/secure access port configuration to prevent rogue devices from joining the maintenance domain - the trade-off is that legitimate CFM peers must be explicitly permitted and unauthorized-but-benign OAM traffic will be discarded. Because there is no persistence or file-system impact, rebooting the FPC or device clears leaked cfmman memory and restores service without removing the underlying exposure. For monitoring, poll the cfmman RSS figure with the vendor command (for example 'show system processes node fpc<num> detail | match cfmman') and treat growth into the gigabyte range as an indicator of compromise signalling an imminent FPC crash. Full details and the vendor's own mitigation guidance are in JSA103144 at https://supportportal.juniper.net/JSA103144.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an instance of CWE-400, Uncontrolled Resource Consumption, located in the Connectivity Fault Management (CFM, IEEE 802.1ag) daemon cfmd and its manager process cfmman on Junos OS Evolved. CFM is an Ethernet OAM protocol used for fault detection and isolation across bridged L2 domains; when it is configured and active, the device accepts CFM continuity-check and related protocol frames from directly connected peers. Certain valid packets cause cfmd to consume CPU cycles without bound while cfmman's resident memory grows over successive processing, ultimately exhausting resources on the Flexible PIC Concentrator (FPC) and forcing a crash and restart of the line card, with continued packet processing sustaining the outage. The vendor vector is CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L, and the independent assessment is consistent with CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - no confidentiality or integrity impact, unauthenticated, no user interaction, but a strict adjacency prerequisite. Because the attacker must sit on a directly connected L2 segment and CFM must be enabled, exposure is limited to deployments that peer with untrusted or partially trusted devices on the same broadcast domain.
Know when Junos Os Evolved 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:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/V:C/RE:M/U:Green
Adjacent unauthenticated attacker sending low-complexity valid CFM traffic (AV:A/AC:L/PR:N/UI:N); availability-only impact with FPC crash so C:N/I:N/A:H.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
DescriptionCVE.org
An Uncontrolled Resource Consumption vulnerability in the Connectivity Fault Management (CFM) daemon and the Connectivity Fault Management Manager (cfmman) of Juniper Networks Junos OS Evolved on PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008, PTX10016 allows an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS).
An attacker on an adjacent device sending specific valid traffic can cause cfmd to spike the CPU to 100% and cfmman's memory to leak, eventually to cause the FPC crash and restart.
Continued receipt and processes of these specific valid packets will sustain the Denial of Service (DoS) condition.
An indicator of compromise is to watch for an increase in cfmman memory rising over time by issuing the following command and evaluating the RSS number. If the RSS is growing into GBs then consider restarting the device to temporarily clear memory.
user@device> show system processes node fpc<num> detail | match cfmman
Example:
show system processes node fpc0 detail | match cfmman F S UID PID PPID PGID SID C PRI NI ADDR SZ WCHAN RSS PSR STIME TTY TIME CMD 4 S root 15204 1 15204 15204 0 80 0 - 90802 - 113652 4 Sep25 ? 00:15:28 /usr/bin/cfmman -p /var/pfe -o -c /usr/conf/cfmman-cfg-active.xml This issue affects Junos OS Evolved on PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008, PTX10016:
- from 23.2R1-EVO before 23.2R2-S4-EVO,
- from 23.4 before 23.4R2-S4-EVO,
- from 24.2 before 24.2R2-EVO,
- from 24.4 before 24.4R1-S2-EVO, 24.4R2-EVO.
This issue does not affect Junos OS Evolved on PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008, PTX10016 before 23.2R1-EVO.
Executive ViewAI
Juniper Junos OS Evolved on PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008, and PTX10016 platforms (releases 23.2R1-EVO and later) with Connectivity Fault Management (CFM) configured is vulnerable to a denial-of-service condition from an adjacent Layer 2 segment. This could cause line card crashes and restarts, disrupting network availability for organizations relying on these routers for core or edge services. Publicly available exploit code exists, but exploitation requires local network access and specific CFM configuration, making this a moderate-priority operational risk rather than an immediate emergency.
No vendor-released patch identified at time of analysis. Interim mitigations: disable CFM if not required; restrict Layer 2 access to trusted devices; monitor cfmd CPU and cfmman memory usage.
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.
Affected Products (CPE)CVE.org
More in Junos Os Evolved
View allAn Improper Handling of Exceptional Conditions vulnerability in Juniper Networks Junos OS and Junos OS Evolved allows an
An Exposure of Resource to Wrong Sphere vulnerability in the sampling service of Juniper Networks Junos OS Evolved allow
Unauthenticated OS command injection in Juniper Networks Junos OS Evolved's bootzd zero-touch provisioning (ZTP) daemon
An improper check for unusual or exceptional conditions in Juniper Networks Junos OS and Junos OS Evolved Routing Protoc
Authenticated, low-privileged TACACS+ users on Juniper Networks Junos OS Evolved can escalate to root and execute arbitr
A Missing Release of File Descriptor or Handle after Effective Lifetime vulnerability in plugable authentication module
Unauthenticated OS command injection in the bootzd zero-touch provisioning (ZTP) daemon of Juniper Networks Junos OS Evo
OS command injection in the phcd phone-home daemon of Juniper Networks Junos OS and Junos OS Evolved lets an adjacent, u
Heap-based buffer overflow in the sdxd service-deployment daemon of Juniper Networks Junos OS and Junos OS Evolved allow
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
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB