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

Published Oct 9, 2025
·
Updated

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.

Affected Software

31 affected components
Juniper Networks Junos OS
All of the following
Any of the following
Juniper Junos<21.4
Juniper Junos=21.4
Juniper Junos=21.4-r1
Juniper Junos=21.4-r1-s1
Juniper Junos=21.4-r1-s2
Juniper Junos=21.4-r2
Juniper Junos=21.4-r2-s1
Juniper Junos=21.4-r2-s2
Juniper Junos=22.2
Juniper Junos=22.2-r1
Juniper Junos=22.2-r1-s1
Juniper Junos=22.2-r1-s2
Juniper Junos=22.2-r2
Juniper Junos=22.2-r2-s1
Juniper Junos=22.2-r2-s2
Juniper Junos=22.2-r3
Juniper Junos=22.2-r3-s1
Juniper Junos=22.2-r3-s2
Any of the following
Juniper EX4600
Juniper EX4650
Juniper QFX5110
Juniper QFX5120
Juniper Qfx5130
Juniper QFX5200
Juniper QFX5210
Juniper QFX5220
Juniper Qfx5230-64cd
Juniper Qfx5240
Juniper Qfx5241
Juniper Qfx5700

Remediation

Information

The following software releases have been updated to resolve this specific issue: 21.4R3, 22.2R3-S3, 22.3R1, and all subsequent releases.

Event History

Oct 9, 2025
CVE Published
via MITRE·03:43 PM
Data Sourced
via MITRE·03:43 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-59957?

CVE-2025-59957 is considered a high severity vulnerability due to the potential for an unauthenticated attacker with physical access to compromise the system.

2

How do I fix CVE-2025-59957?

To fix CVE-2025-59957, ensure that physical security measures are in place to prevent unauthorized access to the Juniper Networks devices.

3

What systems are affected by CVE-2025-59957?

CVE-2025-59957 affects Juniper Networks Junos OS on EX4600 Series and QFX5000 Series hardware.

4

What can an attacker do if they exploit CVE-2025-59957?

If exploited, an attacker can create a backdoor that provides complete control over the affected Junos OS device.

5

How can I mitigate the risk of CVE-2025-59957?

Mitigation of CVE-2025-59957 includes implementing strict physical security protocols and monitoring access to the Juniper Networking equipment.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203