CVE-2026-33780
Received Received - Intake
Memory Leak in Juniper l2ald Causes Denial of Service

Publication date: 2026-04-09

Last updated on: 2026-04-17

Assigner: Juniper Networks, Inc.

Description
A Missing Release of Memory after Effective Lifetime vulnerability in the Layer 2 Address Learning Daemon (l2ald) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause a memory leak ultimately leading to a Denial of Service (DoS). In an EVPN-MPLS scenario, routes learned from remote multi-homed Provider Edge (PE) devices are programmed as ESI routes. Due to a logic issue in the l2ald memory management, memory allocated for these routes is not released when there is churn for these routes. As a result, memory leaks in the l2ald process which will ultimately lead to a crash and restart of l2ald. Use the following command to monitor the memory consumption by l2ald: user@device> show system process extensive | match "PID|l2ald" This issue affects: Junos OS: * all versions before 22.4R3-S5, * 23.2 versions before 23.2R2-S3, * 23.4 versions before 23.4R2-S4, * 24.2 versions before 24.2R2; Junos OS Evolved: * all versions before 22.4R3-S5-EVO, * 23.2 versions before 23.2R2-S3-EVO, * 23.4 versions before 23.4R2-S4-EVO, * 24.2 versions before 24.2R2-EVO.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-09
Last Modified
2026-04-17
Generated
2026-05-07
AI Q&A
2026-04-10
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 63 associated CPEs
Vendor Product Version / Range
juniper junos 22.4
juniper junos 22.4
juniper junos 22.4
juniper junos 22.4
juniper junos 23.2
juniper junos 22.4
juniper junos 23.2
juniper junos 22.4
juniper junos 22.4
juniper junos 22.4
juniper junos 23.2
juniper junos 23.2
juniper junos 23.4
juniper junos 23.4
juniper junos 22.4
juniper junos 22.4
juniper junos 23.4
juniper junos 23.2
juniper junos 24.2
juniper junos 24.2
juniper junos 23.4
juniper junos 22.4
juniper junos 22.4
juniper junos 23.2
juniper junos 23.2
juniper junos 23.4
juniper junos 23.4
juniper junos 23.4
juniper junos 23.4
juniper junos 24.2
juniper junos to 22.4 (exc)
juniper junos 24.2
juniper junos_os_evolved 22.4
juniper junos_os_evolved 22.4
juniper junos_os_evolved 22.4
juniper junos_os_evolved 22.4
juniper junos_os_evolved 23.2
juniper junos_os_evolved 23.2
juniper junos_os_evolved 23.2
juniper junos_os_evolved 22.4
juniper junos_os_evolved 22.4
juniper junos_os_evolved 22.4
juniper junos_os_evolved 23.2
juniper junos_os_evolved 23.2
juniper junos_os_evolved 23.2
juniper junos_os_evolved 22.4
juniper junos_os_evolved 24.2
juniper junos_os_evolved 24.2
juniper junos_os_evolved 23.4
juniper junos_os_evolved 23.4
juniper junos_os_evolved 23.4
juniper junos_os_evolved 23.2
juniper junos_os_evolved 22.4
juniper junos_os_evolved 22.4
juniper junos_os_evolved to 22.4 (exc)
juniper junos_os_evolved 23.4
juniper junos_os_evolved 23.4
juniper junos_os_evolved 22.4
juniper junos_os_evolved 22.4
juniper junos_os_evolved 23.4
juniper junos_os_evolved 23.4
juniper junos_os_evolved 23.4
juniper junos_os_evolved 24.2
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-401 The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a Missing Release of Memory after Effective Lifetime issue in the Layer 2 Address Learning Daemon (l2ald) of Juniper Networks Junos OS and Junos OS Evolved.

It allows an adjacent, unauthenticated attacker to cause a memory leak by exploiting a logic issue in the l2ald memory management when handling routes learned from remote multi-homed Provider Edge (PE) devices in an EVPN-MPLS scenario.

Because memory allocated for these routes is not released properly during route churn, the l2ald process leaks memory, which ultimately leads to a crash and restart of the l2ald daemon.


How can this vulnerability impact me? :

The primary impact of this vulnerability is a Denial of Service (DoS) condition.

An attacker who is adjacent and unauthenticated can exploit the memory leak to cause the l2ald process to consume increasing amounts of memory until it crashes and restarts.

This crash and restart can disrupt network operations that depend on the l2ald daemon, potentially causing network instability or outages.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring the memory consumption of the l2ald process on affected Juniper devices.

You can use the following command to check the memory usage of the l2ald process:

  • show system process extensive | match "PID|l2ald"

What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, you should upgrade your Junos OS or Junos OS Evolved to a fixed version that addresses the memory leak issue in the l2ald process.

  • For Junos OS, upgrade to versions 22.4R3-S5 or later, 23.2R2-S3 or later, 23.4R2-S4 or later, or 24.2R2 or later.
  • For Junos OS Evolved, upgrade to versions 22.4R3-S5-EVO or later, 23.2R2-S3-EVO or later, 23.4R2-S4-EVO or later, or 24.2R2-EVO or later.

Additionally, monitor the memory consumption of the l2ald process using the command: show system process extensive | match "PID|l2ald" to detect abnormal memory usage that could indicate the vulnerability is being exploited.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart