CVE-2026-21919 | Junos OS and Junos OS Evolved: A high frequency of connecting and disconnecting NETCONF sessions causes management unavailability

An Incorrect Synchronization vulnerability in the management daemon (mgd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based attacker with low privileges to cause a complete Denial-of-Service (DoS) of the management plane. When NETCONF sessions are quickly established and disconnected, a locking issue causes mgd processes to hang in an unusable state. When the maximum number of mgd processes has been reached, no new logins are possible. This leads to the inability to manage the device and requires a power-cycle to recover. This issue can be monitored by checking for mgd processes in lockf state in the output of 'show system processes extensive': user@host> show system processes extensive | match mgd <pid> root       20   0 501M 4640K lockf   1 0:01 0.00% mgd If the system still can be accessed (either via the CLI or as root, which might still be possible as last resort as this won't invoke mgd), mgd processes in this state can be killed with 'request system process terminate <PID>' from the CLI or with 'kill -9 <PID>' from the shell.  This issue affects: Junos OS: * 23.4 versions before 23.4R2-S4, * 24.2 versions before 24.2R2-S1, * 24.4 versions before 24.4R1-S3, 24.4R2; This issue does not affect Junos OS versions before 23.4R1; Junos OS Evolved: * 23.4 versions before 23.4R2-S5-EVO, * 24.2 versions before 24.2R2-S1-EVO, * 24.4 versions before 24.4R1-S3-EVO, 24.4R2-EVO. This issue does not affect Junos OS Evolved versions before 23.4R1-EVO;

Published: 2026-04-09 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-21919 is rated Low Risk (33.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.23%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-21919

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 0.23% +0.18%
2 2026-05-11 0.04% 0.05% +0.02%
3 2026-04-10 0.04%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-21919

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 4.0 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/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:Y/R:U/V:X/RE:M/U:X Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network.
Attack complexity (AC:L)
Exploitation conditions are straightforward and stable.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:L)
Low privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:N)
No confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:N)
No integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:H)
High availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N)
No availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:Y)
Yes: all four kill-chain steps (reconnaissance, weaponization, delivery, exploitation) can be automated.
Recovery (supplemental) (R:U)
User: manual user intervention is needed to recover services.
Value density (supplemental) (V:X)
Not evaluated.
Vulnerability response effort (supplemental) (RE:M)
Moderate effort (remote update, disable subsystem, simple upgrade with minor service impact).
Provider urgency (supplemental) (U:X)
Not evaluated.
[email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 3.6 [email protected]

Weakness enumeration for CVE-2026-21919

Affected software / configurations for CVE-2026-21919

Vendor Product Version Raw CPE
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:-:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r1:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r1-s1:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r1-s2:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r2:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r2-s1:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r2-s2:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r2-s3:*:*:*:*:*:*
juniper junos 24.2 cpe:2.3:o:juniper:junos:24.2:-:*:*:*:*:*:*
juniper junos 24.2 cpe:2.3:o:juniper:junos:24.2:r1:*:*:*:*:*:*
juniper junos 24.2 cpe:2.3:o:juniper:junos:24.2:r1-s1:*:*:*:*:*:*
juniper junos 24.2 cpe:2.3:o:juniper:junos:24.2:r1-s2:*:*:*:*:*:*
juniper junos 24.2 cpe:2.3:o:juniper:junos:24.2:r2:*:*:*:*:*:*
juniper junos 24.4 cpe:2.3:o:juniper:junos:24.4:-:*:*:*:*:*:*
juniper junos 24.4 cpe:2.3:o:juniper:junos:24.4:r1:*:*:*:*:*:*
juniper junos 24.4 cpe:2.3:o:juniper:junos:24.4:r1-s2:*:*:*:*:*:*
juniper junos 24.4 cpe:2.3:o:juniper:junos:24.4:r2:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:-:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r1:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r1-s1:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r1-s2:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r2:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r2-s1:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r2-s2:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r2-s3:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r2-s4:*:*:*:*:*:*
juniper junos_os_evolved 24.2 cpe:2.3:o:juniper:junos_os_evolved:24.2:-:*:*:*:*:*:*
juniper junos_os_evolved 24.2 cpe:2.3:o:juniper:junos_os_evolved:24.2:r1:*:*:*:*:*:*
juniper junos_os_evolved 24.2 cpe:2.3:o:juniper:junos_os_evolved:24.2:r1-s2:*:*:*:*:*:*
juniper junos_os_evolved 24.2 cpe:2.3:o:juniper:junos_os_evolved:24.2:r2:*:*:*:*:*:*
juniper junos_os_evolved 24.4 cpe:2.3:o:juniper:junos_os_evolved:24.4:-:*:*:*:*:*:*
juniper junos_os_evolved 24.4 cpe:2.3:o:juniper:junos_os_evolved:24.4:r1:*:*:*:*:*:*
juniper junos_os_evolved 24.4 cpe:2.3:o:juniper:junos_os_evolved:24.4:r1-s2:*:*:*:*:*:*
juniper junos_os_evolved 24.4 cpe:2.3:o:juniper:junos_os_evolved:24.4:r2:*:*:*:*:*:*

References for CVE-2026-21919

URL Tags
https://kb.juniper.net/JSA106019 Mitigation Vendor Advisory
cvelogic Threat Intelligence