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

Published Apr 9, 2026
·
Updated

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;

Affected Software

36 affected components
Juniper Networks Junos OS>=23.4R1<23.4R2-S4, >=24.2R1<24.2R2-S1, >=24.4R1<24.4R1-S3, =24.4R2
Juniper Networks Junos OS Evolved>=23.4R1-EVO<23.4R2-S5-EVO, >=24.2R1-EVO<24.2R2-S1-EVO, >=24.4R1-EVO<24.4R1-S3-EVO, =24.4R2-EVO
Juniper Junos=23.4
Juniper Junos=23.4-r1
Juniper Junos=23.4-r1-s1
Juniper Junos=23.4-r1-s2
Juniper Junos=23.4-r2
Juniper Junos=23.4-r2-s1
Juniper Junos=23.4-r2-s2
Juniper Junos=23.4-r2-s3
Juniper Junos=24.2
Juniper Junos=24.2-r1
Juniper Junos=24.2-r1-s1
Juniper Junos=24.2-r1-s2
Juniper Junos=24.2-r2
Juniper Junos=24.4
Juniper Junos=24.4-r1
Juniper Junos=24.4-r1-s2
Juniper Junos=24.4-r2
Juniper Junos OS Evolved=23.4
Juniper Junos OS Evolved=23.4-r1
Juniper Junos OS Evolved=23.4-r1-s1
Juniper Junos OS Evolved=23.4-r1-s2
Juniper Junos OS Evolved=23.4-r2
Juniper Junos OS Evolved=23.4-r2-s1
Juniper Junos OS Evolved=23.4-r2-s2
Juniper Junos OS Evolved=23.4-r2-s3
Juniper Junos OS Evolved=23.4-r2-s4
Juniper Junos OS Evolved=24.2
Juniper Junos OS Evolved=24.2-r1
Juniper Junos OS Evolved=24.2-r1-s2
Juniper Junos OS Evolved=24.2-r2
Juniper Junos OS Evolved=24.4
Juniper Junos OS Evolved=24.4-r1
Juniper Junos OS Evolved=24.4-r1-s2
Juniper Junos OS Evolved=24.4-r2

Remediation

Information

The following software releases have been updated to resolve this specific issue: Junos OS Evolved: 23.4R2-S5-EVO, 24.2R2-S1-EVO, 24.4R1-S3-EVO, 24.4R2-EVO, 25.2R1-EVO, and all subsequent releases; Junos OS: 23.4R2-S4, 24.2R2-S1, 24.4R1-S3, 24.4R2, 25.2R1, and all subsequent releases.

Event History

Apr 9, 2026
CVE Published
via MITRE·09:26 PM
Data Sourced
via MITRE·09:26 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-21919?

CVE-2026-21919 has been identified with a high severity due to its impact on management availability.

2

How do I fix CVE-2026-21919?

To fix CVE-2026-21919, you should upgrade to the patched versions of Junos OS or Junos OS Evolved as specified in the vendor's advisory.

3

What systems are affected by CVE-2026-21919?

CVE-2026-21919 affects Juniper Networks Junos OS and Junos OS Evolved versions within certain ranges.

4

What causes CVE-2026-21919?

CVE-2026-21919 is caused by incorrect synchronization in the management daemon leading to frequent connection issues.

5

Who can exploit CVE-2026-21919?

CVE-2026-21919 can be exploited by a network-based attacker with low privilege access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203