CVE-2025-59957 | Junos OS: EX4600 Series and QFX5000 Series: An attacker with physical access can open a persistent backdoor

An Origin Validation Error vulnerability in an insufficient protected file of Juniper Networks Junos OS on EX4600 Series and QFX5000 Series allows an unauthenticated attacker with physical access to the device to create a backdoor which allows complete control of the system. When a device isn't configured with a root password, an attacker can modify a specific file. It's contents will be added to the Junos configuration of the device without being visible. This allows for the addition of any configuration unknown to the actual operator, which includes users, IP addresses and other configuration which could allow unauthorized access to the device. This exploit is persistent across reboots and even zeroization. The indicator of compromise is a modified /etc/config/<platform>-defaults[-flex].conf file. Review that file for unexpected configuration statements, or compare it to an unmodified version which can be extracted from the original Juniper software image file. For details on the extraction procedure please contact Juniper Technical Assistance Center (JTAC). To restore the device to a trusted initial configuration the system needs to be reinstalled from physical media.  This issue affects Junos OS on EX4600 Series and QFX5000 Series: * All versions before 21.4R3, * 22.2 versions before 22.2R3-S3.

Published: 2025-10-09 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-59957 is rated Low Risk (30.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.17%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-59957

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.17% +0.16%
2 2025-10-10 0.01%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-59957

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.0 4.0 HIGH
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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:N/R:U/V:X/RE:H/U:X Click to expand
Attack vector (AV:P)
Physical access is required.
Attack complexity (AC:L)
Exploitation conditions are straightforward and stable.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:N)
No privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:H)
High confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:H)
High integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:H)
High availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N)
No availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:N)
No: attackers cannot reliably automate reconnaissance through exploitation for this issue.
Recovery (supplemental) (R:U)
User: manual user intervention is needed to recover services.
Value density (supplemental) (V:X)
Not evaluated.
Vulnerability response effort (supplemental) (RE:H)
High/significant effort (privileged updates, firmware/microcode, depot repair, or strong scheduling impact).
Provider urgency (supplemental) (U:X)
Not evaluated.
[email protected]
6.8 3.1 MEDIUM
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:P)
Hands-on access—USB, keyboard, opening the case—not something you do purely over the wire.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
0.9 5.9 [email protected]

Weakness enumeration for CVE-2025-59957

Affected software / configurations for CVE-2025-59957

Vendor Product Version Raw CPE
juniper junos < 21.4 cpe:2.3:o:juniper:junos:*:*:*:*:*:*:*:*
juniper junos 21.4 cpe:2.3:o:juniper:junos:21.4:-:*:*:*:*:*:*
juniper junos 21.4 cpe:2.3:o:juniper:junos:21.4:r1:*:*:*:*:*:*
juniper junos 21.4 cpe:2.3:o:juniper:junos:21.4:r1-s1:*:*:*:*:*:*
juniper junos 21.4 cpe:2.3:o:juniper:junos:21.4:r1-s2:*:*:*:*:*:*
juniper junos 21.4 cpe:2.3:o:juniper:junos:21.4:r2:*:*:*:*:*:*
juniper junos 21.4 cpe:2.3:o:juniper:junos:21.4:r2-s1:*:*:*:*:*:*
juniper junos 21.4 cpe:2.3:o:juniper:junos:21.4:r2-s2:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:-:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:r1:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:r1-s1:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:r1-s2:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:r2:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:r2-s1:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:r2-s2:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:r3:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:r3-s1:*:*:*:*:*:*
juniper junos 22.2 cpe:2.3:o:juniper:junos:22.2:r3-s2:*:*:*:*:*:*

References for CVE-2025-59957

cvelogic Threat Intelligence