# CVE-2026-127276: Linksys EA8100 Web UI cookie httponly flag


- **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:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-gwfv-r9h8-x85p

## What is CVE-2026-127276?

CVE-2026-127276 is a medium-severity vulnerability in Linksys EA8100, published on 13 Nov 2026. 

### Official description

A vulnerability was identified in Linksys EA8100 1.0.3.216940. Impacted is an unknown function of the component Web UI. Such manipulation leads to cookie without 'httponly' flag. It is possible to launch the attack remotely. This attack is characterized by high complexity. The exploitability is considered difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-1004 (Sensitive Cookie Without 'HttpOnly' Flag)

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

It affects 1 product.


Products: Linksys EA8100.

CPE match criteria (CPE 2.3):

- `cpe:2.3:h:linksys:ea8100:*:*:*:*:*:*:*:*` from 1.0.3.216940 up to 1.0.3.216940

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

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

## Is CVE-2026-127276 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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