# CVE-2026-102174: Memory corruption in Junos OS

> Authenticated VPN clients can trigger a stack buffer overflow in iked to execute root code or cause DoS when JIMS identity publishing is enabled.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-fmx5-gpxg-52jp

## What is CVE-2026-102174?

CVE-2026-102174 is a high-severity memory corruption vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Stack-based Buffer Overflow vulnerability in the iked IKE key-management daemon of Juniper Networks Junos OS on the SRX Series allows an authenticated remote-access VPN client to execute code with root privileges or cause denial of service via the remote-access VPN authentication and JIMS identity-publishing path.

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

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


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

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

## Is CVE-2026-102174 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102174 is a high-severity memory corruption vulnerability in Juniper Networks Junos OS, published on 14 Oct 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-102174 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-102174/ (Markdown: https://insights.sbomify.com/CVE-2026-102174/index.md)
```

## Sources

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

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