# CVE-2026-11505: GL.iNet XE3000 glnassys hard-coded key

> Attackers can exploit a hard-coded cryptographic key in GL.iNet routers to bypass security controls, requiring a firmware upgrade to mitigate.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-2r8p-5hq4-h3r4

## What is CVE-2026-11505?

CVE-2026-11505 is a low-severity vulnerability in GL.iNet A1300, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in GL.iNet A1300, AX1800, AXT1800, MT2500, MT3000, MT6000, X3000 and XE3000 4.8.x. This affects an unknown function of the component glnassys. Executing a manipulation can lead to use of hard-coded cryptographic key
 . The attack may be launched remotely. The attack requires a high level of complexity. The exploitability is reported as difficult. Upgrading to version 4.9.0 mitigates this issue. Upgrading the affected component is advised.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

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


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

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

## Is CVE-2026-11505 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11505 is a low-severity vulnerability in GL.iNet A1300, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11505 in the wild and no public exploit code.

Affected product: GL.iNet A1300. 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-11505/ (Markdown: https://insights.sbomify.com/CVE-2026-11505/index.md)
```

## Sources

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

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