# CVE-2026-33799: Junos OS and Junos OS Evolved: Receipt of a specific SNMPv3 request results in memory leak and eventual snmpd crash

> An authenticated attacker can cause a memory leak and crash the SNMP daemon by sending specific SNMPv3 requests, disrupting system monitoring.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/AU:Y/R:A/V:C/RE:M/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-x7c3-q65h-rwrm

## What is CVE-2026-33799?

CVE-2026-33799 is a medium-severity memory corruption vulnerability in Juniper Junos, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Out-of-bounds Write vulnerability in the SNMP daemon (snmpd) of Juniper Networks Junos OS and Junos OS Evolved allows an authenticated network-based attacker sending specific valid SNMPv3 queries to trigger a memory leak. Over time, continuous receipt of these queries will result in snmpd process memory exhaustion, resulting in a process crash and restart, impacting the ability to monitor the system via SNMP.

Memory usage can be monitored using the following command:

user@device> show system processes extensive | match snmpd

This issue affects:

Junos OS:

  *  all versions before 21.2R3-S8;
  *  from 21.4 before 21.4R3-S7;
  *  from 22.1 before 22.1R3-S6;
  *  from 22.2 before 22.2R3-S4;
  *  from 22.3 before 22.3R3-S3;
  *  from 22.4 before 22.4R3-S2;
  *  from 23.2 before 23.2R2;
  *  from 23.4 before 23.4R2.

Junos OS Evolved:
  *  all versions before 21.2R3-S8-EVO;
  *  from 21.4 before 21.4R3-S7-EVO;
  *  all versions of 22.1-EVO,
  *  from 22.2 before 22.2R3-S4-EVO;
  *  from 22.3 before 22.3R3-S3-EVO;
  *  all versions of 22.4-EVO,
  *  from 23.2 before 23.2R2-EVO;
  *  from 23.4 before 23.4R2-EVO.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-33799?

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

## How do I fix CVE-2026-33799?

No fix has been published for CVE-2026-33799 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33799 being exploited?

There is no known exploitation of CVE-2026-33799 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33799 and fix it if it is affected.

What it is: CVE-2026-33799 is a medium-severity memory corruption vulnerability in Juniper Junos, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33799 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33799/ (Markdown: https://insights.sbomify.com/CVE-2026-33799/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33799
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33799
- OSV: https://osv.dev/vulnerability/CVE-2026-33799

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33799/
Summaries are generated and may contain mistakes; the official description above is the record.