# CVE-2026-102045: Junos OS Evolved: An crafted LACP frame causes lacpd to crash when LACP is enabled

> A crafted LACP frame causes a denial of service in Junos OS Evolved when LACP is enabled on aggregated Ethernet ports.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-q5wg-vxc8-v2rp

## What is CVE-2026-102045?

CVE-2026-102045 is a high-severity memory corruption vulnerability in Juniper Networks Junos OS Evolved, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Out-of-bounds Write Out-of-bounds Write vulnerability in lacpd of Juniper Networks Junos OS Evolved allows a Layer-2-adjacent attacker to cause a denial of service via a crafted frame received on an LACP-enabled aggregated-Ethernet member port.

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

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


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

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

## Is CVE-2026-102045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102045 is a high-severity memory corruption vulnerability in Juniper Networks Junos OS Evolved, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102045 in the wild and no public exploit code.

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

## Sources

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

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