# CVE-2026-102182: Junos OS: MX Series: Certificate-based IKE packets cause root-level code execution

> Unauthenticated attackers can execute root-level code on Juniper MX Series routers via crafted IKE packets due to a stack-based buffer overflow.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/V:C/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-pvg7-92rm-23q6

## What is CVE-2026-102182?

CVE-2026-102182 is a critical memory corruption vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Stack-based Buffer Overflow vulnerability in the kmd component of Juniper Networks Junos OS on MX Series allows an unauthenticated network attacker to execute code as root via specific IKE certificate-based packets.

This issue requires IKE to be enabled with an RSA-signature IKE policy to be vulnerable.

This issue affects Junos OS on MX Series:

  *  All versions before 21.2R3-S11;
  *  from 21.4 before 21.4R3-S12;
  *  from 22.2 before 22.2R3-S8;
  *  from 22.3 before 22.3R3-S5;
  *  from 22.4 before 22.4R3-S9;

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-102182 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102182 is a critical memory corruption vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102182 in the wild and no public exploit code.

Affected product: Juniper Networks Junos OS. 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-102182/ (Markdown: https://insights.sbomify.com/CVE-2026-102182/index.md)
```

## Sources

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

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