Skip to main content
CISA Known Exploited Vulnerabilities

Juniper Junos OS Improper Isolation or Compartmentalization Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2025-03-13
Remediation due
2025-04-03

Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes
https://supportportal.juniper.net/s/article/2025-03-Out-of-Cycle-Security-Bulletin-Junos-OS-A-local-attacker-with-shell-access-can-execute-arbitrary-code-CVE-2025-21590?language=en_US ; https://nvd.nist.gov/vuln/detail/CVE-2025-21590

Description

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.

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2025-21590 to the KEV catalog 1 day after its CVE record was published. The median for entries added in 2025 is 26 days.
  • It is one of 8 Juniper entries in the CISA KEV catalog, and one of 2 added in 2025.
  • Its current EPSS score (1.7%) is higher than that of 6% of CISA KEV entries.

Severity

CVSS 3.1 · CNA · Base score4.4 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:NOpen in CVSS calculator
CVSS 4.0 · CNA · CVSS-B6.7 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableno
Technical impacttotal

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
3 days
and forensic triage
Asset not publicly exposed
14 days
KEV due date
2025-04-03
21 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2025-03-14).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
Juniper Networks
Junos OS
0 to <21.2R3-S9
21.4 to <21.4R3-S10
22.2 to <22.2R3-S6
22.4 to <22.4R3-S6
23.2 to <23.2R2-S3
23.4 to <23.4R2-S4
24.2 to <24.2R1-S2, 24.2R2

Solutions and Workarounds

from the CNA's CVE record

Solution

The following software releases have been updated to resolve this specific issue: 21.2R3-S9, 21.4R3-S10, 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S4, 24.2R1-S2, 24.2R2, 24.4R1, and all subsequent releases.   Please note that this issue is not fixed for all platforms in the releases specified in the solution section. For the following products the fix is only available in these releases: SRX300 Series   21.2R3-S9, 23.4R2-S5*, 24.4R1 SRX550HM    22.2R3-S7* EX4300 Series     21.4R3-S11* (except EX4300-48MP which has fixes available as indicated in the solution) EX4600               21.4R3-S11* (except EX4650 which has fixes available as indicated in the solution) ACX1000, ACX1100, ACX2100, ACX2200, ACX4000, ACX500              21.2R3-S9 MX104               21.2R3-S9 * Future Release

Workarounds

It is strongly recommended to mitigate the risk of exploitation by restricting shell access to trusted users only.

References

2 links

Record Details

Published
2025-03-12
Last updated
2026-02-26
Assigner (CNA)
juniper
Credited to
Juniper SIRT would like to acknowledge and thank Matteo Memelli from Amazon for responsibly reporting this issue. Note: Amazon found the issue during internal security research and not due to exploitation.

More from Juniper Networks

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.