# CVE-2026-121616: Linksys E5600 JSON Request mesh_login.cgi strcpy out-of-bounds write


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-rqwp-qx4w-fv82

## What is CVE-2026-121616?

CVE-2026-121616 is a medium-severity vulnerability in Linksys E5600, published on 4 Nov 2026. 

### Official description

A vulnerability was identified in Linksys E5600 1.1.0.26. Affected by this vulnerability is the function strcpy of the file /cgi-bin/mesh_login.cgi of the component JSON Request Parser. The manipulation of the argument username/password/token/source/cn/action leads to out-of-bounds write. The attack may be initiated remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-121616 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121616 is a medium-severity vulnerability in Linksys E5600, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121616 exists.

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

## Sources

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

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