# CVE-2026-101974: Information disclosure in Junos OS

> Adjacent OSPF peers can disclose memory or crash the routing process via malformed packets when link-local TE is enabled.

- **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`)
- **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:** 29 Oct 2026
- **Also known as:** GHSA-94wf-w5qv-6v9g

## What is CVE-2026-101974?

CVE-2026-101974 is a high-severity vulnerability in Juniper Networks Junos OS, 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 Improper Validation of Specified Quantity in Input vulnerability in rpd of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent OSPF peer to disclose rpd memory or cause a rpd crash via a malformed OSPF packets.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

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


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

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

## Is CVE-2026-101974 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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