IRONSMITHINTEL
MEDIUMCVSS4.4
|
Actively Exploited
|CISA KEV|CVE-2025-21590|Auth: high — administrative privileges|Reboot: required|Manual only

Juniper Junos OS Improper Isolation or Compartmentalization Vulnerability (CVE-2025-21590)

Juniper Junos OS contains an improper isolation or compartmentalization vulnerability. This vulnerability could allows a local attacker with high privileges to inject arbitrary code.

Published Mar 12, 2025 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A local attacker, with administrative privileges, can achieve partial data exposure, arbitrary modification of data. Federal agencies are required to remediate by 2025-04-03 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-653) (CWE-653) vulnerability in Juniper Junos OS. An Improper Isolation or Compartmentalization vulnerability in the kernel of Juniper Networks Junos OS allows a local attacker with high privileges to compromise the integrity of the device. A local attacker with access to the shell is able to inject arbitrary code which can compromise an affected device. This issue is not exploitable from the Junos CLI. This issue affects Junos OS:  * All versions before 21.2R3-S9, * 21.4 versions before 21.4R3-S10,  * 22.2 versions before 22.2R3-S6,  * 22.4 versions before 22.4R3-S6,  * 23.2 versions before 23.2R2-S3,  * 23.4 versions before 23.4R2-S4, * 24.2 versions before 24.2R1-S2, 24.2R2. Exploitation requires local access, low attack complexity, an administrative account, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

Network Security Team
Firewall Administrators
IT Security
Running junos: v ≤ 21.2, 21.2, 21.4, 22.2, 22.4, 23.2, 23.4, 24.2
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-03-13 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-04-03.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2025-21590's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.