Skip to main content
VulnerabilityPublished

CVE-2026-21911: Juniper Networks Junos OS Evolved · Incorrect Calculation

Affects Juniper Networks Junos OS EvolvedSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium · fixed in 23.4R1-S2-EVO : update Juniper Networks Junos OS Evolved when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 23.4R1-S2-EVO, 23.2R2-S1-EVO, 22.4R3-S2-EVO +3
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Juniper NetworksJunos OS EvolvedAffected
  • <21.4R3-S7-EVO
  • >=22.2 <22.2R3-S4-EVO
  • >=22.3 <22.3R3-S3-EVO
  • >=22.4 <22.4R3-S2-EVO
  • >=23.2 <23.2R2-S1-EVO
  • =23.4
Fixed in
  • 23.4R1-S2-EVO
  • 23.2R2-S1-EVO
  • 22.4R3-S2-EVO
  • 22.3R3-S3-EVO
  • 22.2R3-S4-EVO
  • 21.4R3-S7-EVO

AI-suggested

To mitigate CVE-2026-21911, European organizations should promptly upgrade affected Junos OS Evolved devices to the fixed versions listed by Juniper (21.4R3-S7-EVO or later for earlier branches, and corresponding patched releases for 22.2, 22.3, 22.4, 23.2, and 23.4 branches). If you cannot patch yet, organizations should restrict access to management interfaces to trusted and authenticated network segments only, using network segmentation and access control lists (ACLs) to prevent unauthorized network-adjacent attackers from reaching the vulnerable daemon. Monitoring for unusual log flooding and CPU spikes on Juniper devices can help detect attempted exploitation. Additionally, implementing rate limiting on management interface traffic and enabling logging thresholds can reduce the impact of log floods. Network operators should review and harden Layer 2 control protocols and consider disabling unused or unnecessary services related to l2cpd. Regular vulnerability scanning and asset inventory to identify affected Junos OS Evolved versions are essential for timely remediation.

Description

CVE-2026-21911 is an incorrect calculation vulnerability in the Layer 2 Control Protocol Daemon (l2cpd) of Juniper Networks Junos OS Evolved. It allows an unauthenticated network-adjacent attacker to flap the management interface, causing the system to stop learning new MAC addresses over label-switched interfaces and generating excessive logs that lead to high CPU usage. This results in a denial-of-service condition affecting network device availability. The vulnerability affects multiple versions of Junos OS Evolved prior to specific patched releases. Exploitation does not require authentication or user interaction but requires network adjacency. The CVSS score is 6.5 (medium severity) with impact primarily on availability. No known exploits are reported in the wild yet.

References

Community reviews

Loading reviews…