PoC Monitor
← All CVEs
CVE-2026-33775published 9 Apr 2026 21:30 UTCData: JSON · API

Juniper Networks Junos OS

Junos OS: MX Series: Mismatch between configured and received packet types causes memory leak in bbe-smgd

Edge device · Router / network deviceknown edge product: Juniper Networks Junos OS Junos OS: MX Series: (high confidence)

A Missing Release of Memory after Effective Lifetime vulnerability in the BroadBand Edge subscriber management daemon (bbe-smgd) of Juniper Networks Junos OS on MX Series allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS). If the authentication packet-type option is configured and a received packet does not match that packet type, the memory leak occurs. When all memory available to bbe-smgd has been consumed, no new subscribers will be able to login. The memory utilization of bbe-smgd can be monitored with the following show command: user@host> show system processes extensive | match bbe-smgd The below log message can be observed when this limit has been reached: bbesmgd[<PID>]: %DAEMON-3-SMD_DPROF_RSMON_ERROR: Resource unavailability, Reason: Daemon Heap Memory exhaustion This issue affects Junos OS on MX Series: * all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S5, * 23.4 versions before 23.4R2-S6, * 24.2 versions before 24.2R2-S2, * 24.4 versions before 24.4R2, * 25.2 versions before 25.2R2.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-401
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Juniper Networks Junos OS
  • < 22.4R3-S8
  • >= 23.2, < 23.2R2-S5
  • >= 23.4, < 23.4R2-S6
  • >= 24.2, < 24.2R2-S2
  • >= 24.4, < 24.4R2
  • >= 25.2, < 25.2R2

Fixed in 22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S2, 24.4R2, 25.2R2

Mitigation

The following software releases have been updated to resolve this specific issue: 22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S2, 24.4R2, 25.2R2, 25.4R1, and all subsequent releases.

Workaround

There are no known workarounds for this issue.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published9 Apr 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.