# CVE-2026-114576: Linksys RE6250 Web Management strcmp random values


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-w2w5-phf3-47jv

## What is CVE-2026-114576?

CVE-2026-114576 is a medium-severity vulnerability in Linksys RE6250, published on 22 Oct 2026. 

### Official description

A vulnerability has been found in Linksys RE6250 1.0.04.001. This affects the function strcmp of the component Web Management Interface. The manipulation of the argument session_id leads to insufficiently random values. The attack may be initiated remotely. The complexity of an attack is rather high. It is indicated that the exploitability is difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-310

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


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

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

## Is CVE-2026-114576 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114576 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114576 is a medium-severity vulnerability in Linksys RE6250, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114576 exists.

Affected product: Linksys RE6250. 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-114576/ (Markdown: https://insights.sbomify.com/CVE-2026-114576/index.md)
```

## Sources

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

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