Skip to content
Log inStart free trial

CVE-2025-21590

An Improper Isolation or Compartmentalization vulnerability in the kernel of Juniper Networks Junos OS allows a local attacker with high privileges to…

Medium Known exploited
Severity
6.7 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
1.75%
Chance of exploitation in the next 30 days. Higher than 77.85% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Mar 13, 2025
Weakness
CWE-653 Improper Isolation or Compartmentalization
Fix
None yet
No fixed version published
Exploited in the wild. Juniper Junos OS Improper Isolation or Compartmentalization Vulnerability (Juniper Junos OS). 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. Due for U.S. federal agencies by Apr 3, 2025.

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.

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 4.0 6.7

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/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:X/R:X/V:X/RE:X/U:X

Attack vector
Local
Attack complexity
Low
Attack requirements
None
Privileges required
High
User interaction
None
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
High
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None
Exploit maturity
Not defined
Scope
X

CVSS 3.1 4.4

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Weakness

CWE-653: Improper Isolation or Compartmentalization

The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.

How to prevent it
  • Architecture and Design: Break up privileges between different modules, objects, or entities. Minimize the interfaces between modules and require strong access control between them.

References

Advisories

Other links

Timeline

  1. Published
  2. Added to CISA's Known Exploited Vulnerabilities catalog
  3. Remediation due for U.S. federal agencies
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-69qc-f5m6-889c
Ghost: Stored XSS via Embed Card Previews
High Same weakness, CWE-653
GHSA-fcqc-726x-5wfc
vm2: Sandboxed code can read and write host-realm memory via Node's shared Buffer pool
Critical Same weakness, CWE-653
GHSA-62fc-8686-hfmq
Traefik: `allowCrossNamespace=false` bypass via `@kubernetescrd` TraefikService backendRef
Medium Same weakness, CWE-653
EEF-CVE-2026-65635
Boruta dynamic client registration allows creation of over-privileged OAuth clients
Not rated yet Same weakness, CWE-653
GHSA-9vg3-4rfj-wgcm
vm2 has Sandbox Breakout Through Null Proto Exception
Critical Same weakness, CWE-653
GHSA-vwrp-x96c-mhwq
vm2: Mutable Proxies for Host Intrinsic Prototypes Allows Sandbox Escape
Critical Same weakness, CWE-653
GHSA-47x8-96vw-5wg6
vm2 Access to Host Object Enables Sandbox Escape
Critical Same weakness, CWE-653
GHSA-ffh4-j6h5-pg66
VM2 Has a WASM Sandbox Escape
Critical Same weakness, CWE-653
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor