Skip to content
VulniPulse
Medium6.5Juniper Networks

Medium [CVE-2026-21919] 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

This medium-severity Juniper Networks advisory covers CVE-2026-21919 affecting Junos OS, Junos OS Evolved, Junos.

CVE-2026-21919 Published Apr 9, 2026Updated by vendor Jun 17, 2026
Affected products & platforms
Juniper NetworksJunosJunos OS Evolved
Open vendor advisory

Android app · Google Play

Monitor future Juniper Networks CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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 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 ' from the CLI or with 'kill -9 ' from the shell.

This issue affects:

  • 23.4 versions before 23.4R2-S4,
  • 24.2 versions before 24.2R2-S1,

This issue does not affect Junos OS versions before 23.4R1;

Affected versions
  • 23.4
  • 24.2
  • 24.4

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 23.4R2-S4
  • 24.2R2-S1
  • 24.4R1-S3
  • 23.4R1
  • 23.4R2-S5-EVO
  • 24.2R2-S1-EVO
  • 24.4R1-S3-EVO
  • 23.4R1-EVO

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation

Upgrade to a fixed release: 23.4R2-S4, 24.2R2-S1, 24.4R1-S3, 23.4R1, 23.4R2-S5-EVO, 24.2R2-S1-EVO. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.