Linksys E8450, CVE-2026-120283: a new CVE scored 10
The bottom line
Anyone running a Linksys E8450 on firmware 1.2.00.360516 should act now; the record scores this at 10 out of 10 under CVSS 4.0 and no patch exists. The vendor did not respond to disclosure, so check immediately whether the router's management interface is reachable from outside your network.
At a glance
| Fact | Detail |
|---|---|
| Product | Linksys E8450 (CVE-2026-120283) |
| Severity | Critical: 10 (CVSS 4.0) |
| Status | A new CVE record, published by VulDB on 2 November 2026. Not on CISA's list of exploited vulnerabilities when we read it on 6 November 2026, which means nothing public says yet that anyone is using it. |
| Fixed in | No source we read names a fixed version |
| Who looks first | Operators of a Linksys E8450 running firmware 1.2.00.360516. If you do not run this device, or run it on a different firmware version, this record does not name you. |
Does this apply to you?
| Question | If no | If yes |
|---|---|---|
| Do you operate a Linksys E8450 router? | Nothing to do for this CVE. | Check the firmware version (next question). |
| Is the firmware version 1.2.00.360516? | The record names only that version; monitor for further advisories. | Check whether the management interface is reachable from outside your network. |
| Is the router's management interface reachable from the internet or an untrusted network? | Restrict access to trusted hosts and monitor for a vendor patch. | Restrict access immediately; no patch is available. |
What it is
A remotely exploitable stack-based buffer overflow in the router's portal.cgi handler. An attacker can send a crafted value for the hidden_timezone argument to overflow a stack buffer, which the record says can be done from across a network.
Why it matters
The record scores this at 10 under CVSS 4.0, the maximum possible. A stack-based buffer overflow via a remotely supplied CGI argument means an attacker who can reach the endpoint may overwrite the call stack and run code on the device. Our reading is that a router at the network edge is a high-value target: control of it gives an attacker a position inside the boundary before internal defences can act. The record states the vendor did not respond to the researcher's disclosure, so no official patch exists and no timeline for one is known.
Exposure by situation
These priorities are our judgement from what the sources say about who can use the flaw and how. They are not vendor ratings.
| Your situation | Priority | Timeframe |
|---|---|---|
| Linksys E8450 on 1.2.00.360516 with management interface reachable from the internet | Medium | This week |
| Linksys E8450 on 1.2.00.360516 with management interface on internal LAN only | Medium | Next patch cycle; monitor for vendor update |
| Linksys E8450 on a firmware version other than 1.2.00.360516 | Low | Monitor for further advisories |
| No Linksys E8450 in the estate | None | No action required |
Things people will get wrong
- A score of 10 means this is already being exploited. The score reflects severity if exploited, not confirmed exploitation. The record states this is a new CVE and it is not on CISA's list of exploited vulnerabilities.
- If my firmware version differs, I am safe. The record identifies 1.2.00.360516 as the tested version. It does not say other versions are unaffected; it only names the one that was confirmed.
How we would triage it
This is our judgement.
Step 1: Find which E8450 devices you run and their firmware version
- Log in to each Linksys E8450 admin interface; the firmware version is shown on the status or administration page.
- Record whether the version matches 1.2.00.360516 as named in the record.
Step 2: Restrict access to the management interface
- Disable remote management if it is enabled, so the admin interface is not reachable from outside the local network.
- Confirm no firewall rule or port forward exposes the router's management interface to the internet.
Step 3: Watch for a vendor patch
- The record states the vendor did not respond to disclosure; check Linksys support pages for firmware updates for the E8450.
- Apply any update that addresses CVE-2026-120283 as soon as one is available.
To close it, read the version from the product itself, not from an old inventory, and save the output with the date. If you cannot update today, write down who owns it, the new date, and what limits exposure until then.
Send this to your IT provider
Copy it, change the names and dates, and send it. It is a draft for you to check, not a template tested with any provider.
We are reviewing CVE-2026-120283, a remotely exploitable stack-based buffer overflow in Linksys E8450 firmware version 1.2.00.360516, scored at 10 out of 10 under CVSS 4.0. No patch has been published and the vendor did not respond to the original disclosure. Please confirm whether we run any Linksys E8450 devices, which firmware version each is on, and whether the management interface is accessible from outside our network. As no fixed version is currently available, please advise when a patch is released and confirm what steps have been taken to restrict access in the meantime. We would like written confirmation of the version and steps taken by 9 November 2026.
The weakness behind it
The record classes this as CWE-121 and CWE-119.
Likely ATT&CK mapping
MITRE ATT&CK is a public catalogue of the steps attackers take, from getting in to causing damage. No source has mapped this flaw to it yet, so the steps below are our prediction from what the record says the flaw allows. They are not MITRE's, the vendor's or CISA's, and an attacker may do other things.
| The step, in plain words | Stage of an attack | Why we think so |
|---|---|---|
| Exploit Public-Facing Application (T1190): Breaking in through a service that faces the internet, such as a web server, VPN or login page. | Initial Access: getting in | The vulnerable CGI script is served by the router's web interface, reachable from any host that can reach the device. A remote stack overflow in a public-facing handler would typically serve as the initial entry point. |
| Exploitation for Privilege Escalation (T1068): Using a flaw to gain higher rights than the account had, such as administrator or root. | Privilege Escalation: gaining higher rights | Router web daemons commonly run as root on embedded Linux; exploiting a stack overflow in a CGI handler would likely yield full system privileges, making software-based privilege escalation a probable outcome. |
How to use this: ask your IT provider which control or log would show each step, for example whether sign-in attempts from the internet are recorded. If nobody can answer, that is the gap to close first.
MITRE ATT&CK® is a registered trademark of The MITRE Corporation. Technique names are MITRE's.
The sources, in their words
The CVE record:
A vulnerability was identified in Linksys E8450 1.2.00.360516. Affected is the function strcpy of the file /www/cgi-bin/portal.cgi. Such manipulation of the argument hidden_timezone leads to stack-based buffer overflow. The attack can be executed remotely. The vendor was contacted early about this disclosure but did not respond in any way.
Versions of Linksys E8450 the record lists as affected:
- 1.2.00.360516
The record gives no version ranges. Use the vendor's advisory for the affected versions.
Check your own project
If you build software, you can compare what a project declares with this CVE from a terminal. The tool reads requirements files, package.json, Maven, Gradle, Cargo, CMake and Dockerfile files, runs nothing, and only the CVE id leaves your machine. Naming the CVEs needs no key.
lattice-scan project . --cve CVE-2026-120283Each row says in-range, outside-range, undetermined or lead, with the file and line. That is evidence about what a manifest declares, not about what runs, and a person decides. The verdicts, the CSV columns and a pipeline recipe are in the guide.
Check the servers you run
The same id can be checked against a host. Run this on the machine itself, not on the laptop that deploys to it: it reads installed packages (dpkg, rpm or apk), snaps, the hardware, the running container images with their operating system and packages, and the kernel version, compares them on the spot, and only the CVE ids leave the machine; the inventory stays on it, in ~/.lattice-scan. Naming the CVEs needs no key. Do it on each server after a deployment, and again when a new entry lands.
lattice-scan --cve CVE-2026-120283A match is a candidate for a person to confirm, not a finding. A distribution can fix a CVE under an unchanged version number, so a match is a candidate; on Debian-family hosts the report also shows whether the package's own changelog names the CVE. It reads the names of the running images, not what is inside them; for what an image declares, use the project check on its Dockerfile.
Guide: namiq.io/lattice/guides/choose-your-channel. MCP server (io.namiq/lattice in the MCP registry): namiq.io/lattice. Package: pypi.org/project/lattice-scan, or namiq.io/apt.
- Which way into Lattice fits your job →The command line, the Claude skill or the MCP server: what each needs, what works without a key and how to read the result.
- Lattice, the MCP server →The public graph the command reads, for AI agents over MCP.
- Install and connect →The signed apt repository, the fingerprint, and the connection commands for each client.
What we do not know yet
- Whether authentication is required before the hidden_timezone argument is processed.
- Whether the vendor has acknowledged the vulnerability or intends to release a patch.
- Whether firmware versions other than 1.2.00.360516 are also affected.
- Exploitation is not recorded. That is not the same as none.
- This is a new record: scores, versions and wording can change in the first days, and they are as at 6 November 2026. We read the vendor pages listed under Sources; nothing here has been tested.
- The sections headed "The bottom line", "Does this apply to you?", "What it is", "Why it matters", "Exposure by situation", "Things people will get wrong", "Likely ATT&CK mapping", "How we would triage it" and "Send this to your IT provider" are our interpretation of the sources, not a statement by CISA or the vendor.