dbcve.org
JunosOperating system · Juniper

CVE-2026-33775

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 22.4 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Memory leak vulnerability in Juniper MX Series routers in the bbe-smgd daemon. When authentication packet-type option is configured and a received packet does not match the configured packet type, memory is leaked with each mismatched packet. Eventually all heap memory is exhausted, preventing new subscriber logins (DoS).

MitigationUpgrade Junos OS to a patched version (22.4R3-S8 or later, 23.2R2-S5 or later, 23.4R2-S6 or later, 24.2R2-S2 or later, 24.4R2 or later, or 25.2R2 or later).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:< 22.4= 22.4= 23.2= 23.4= 24.2= 24.4= 25.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Run 'show chassis hardware' or 'show version' to confirm this is an MX Series router
    Affected if Device is NOT a Juniper MX Series router (vulnerability only affects MX Series)
  2. Check Junos version
    Run 'show version' and note the Junos OS version number
    Affected if Version is NOT in the list: < 22.4, 22.4, 23.2, 23.4, 24.2, 24.4, or 25.2 (unaffected versions are not listed)
  3. Verify bbe-smgd daemon is running
    Run 'show system processes' or 'show bbe-smgd status' to confirm the bbe-smgd daemon is active
    Affected if bbe-smgd daemon is not running (vulnerability only triggers in this daemon)
  4. Check for authentication packet-type configuration
    Run 'show configuration | match packet-type' or navigate to the BBE authentication hierarchy (e.g., 'show configuration access-management') and look for the packet-type option under authentication settings
    Affected if The authentication packet-type option is NOT configured (the memory leak only occurs when this specific option is enabled)
  5. Monitor for memory exhaustion symptoms
    Run 'show system memory' or 'show bbe-smgd memory' periodically to check heap usage; look for continuously increasing memory consumption in the bbe-smgd process
    Affected if Memory in bbe-smgd continuously grows without releasing, especially when mismatched packets are received

Device is affected only if it is an MX Series router running a vulnerable Junos version (22.4, 23.2, 23.4, 24.2, 24.4, or 25.2) AND the authentication packet-type option is configured in the BBE settings, causing memory leak symptoms in the bbe-smgd daemon when mismatched packets arrive

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 22.4 or later
Fixed in 22.4
Interim mitigation

Upgrade Junos OS to a patched version (22.4R3-S8 or later, 23.2R2-S5 or later, 23.4R2-S6 or later, 24.2R2-S2 or later, 24.4R2 or later, or 25.2R2 or later).

Recommended fix High confidence

22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S2, 24.4R2, or 25.2R2 (depending on your current branch)

  1. Identify the current Junos OS version running on the MX Series device using 'show version'
  2. Determine which version branch your current code belongs to (22.4, 23.2, 23.4, 24.2, 24.4, or 25.2)
  3. Upgrade to the minimum fixed version for your branch: 22.4R3-S8 or later, 23.2R2-S5 or later, 23.4R2-S6 or later, 24.2R2-S2 or later, 24.4R2 or later, or 25.2R2 or later
  4. After upgrade, monitor bbe-smgd memory usage with 'show system processes extensive | match bbe-smgd' to confirm the leak is resolved
  5. Verify the device is functioning normally and subscribers can log in successfully
Caveat Standard Junos upgrade precautions apply - verify hardware compatibility, schedule maintenance window, and backup configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33775 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data