[KEV] Vulnerability in Juniper Junos OS (CVE-2025-21590)
Summary
Vulnerability in Juniper Junos OS (CVE-2025-21590). Data can be tampered with by attackers. Listed in CISA KEV — actively exploited.
Original description
The description as published by the source.
Juniper Junos OS contains an improper isolation or compartmentalization vulnerability. This vulnerability could allows a local attacker with high privileges to inject arbitrary code.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-21590 has been found in Juniper Junos OS.
Data can be tampered with by attackers. CVSS score: 4.4/10.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Juniper Junos OS CVE-2025-21590" on the vendor's site.
CVE-2025-21590 (Juniper Junos OS) — CWE-653 / CVSS v3 4.4
Attack vector: local / no user interaction
Listed in CISA KEV — actively exploited, treat as top priority.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-653) exists in Juniper Junos OS.
Check the vendor advisory for the affected versions of Juniper Junos OS.
Severity: Medium (CVSS 4.4/10). Data can be tampered with by attackers. Listed in CISA KEV — actively exploited in the wild, treat as top priority.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Juniper Junos OS を使っているサービスとバージョンを洗い出す。
-
2Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory NVD
- advisory sirt@juniper.net
- patch sirt@juniper.net
- web cisa.gov