CVE-2026-11505 — GL.iNet XE3000 glnassys hard-coded key
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (GL.iNet A1300, GL.iNet AX1800, GL.iNet AXT1800…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| GL.iNet | A1300 | version 4.8.* | Vulnerable | CVE Program (cve.org) e CISA ADP |
| GL.iNet | AX1800 | version 4.8.* | Vulnerable | CVE Program (cve.org) e CISA ADP |
| GL.iNet | AXT1800 | version 4.8.* | Vulnerable | CVE Program (cve.org) e CISA ADP |
| GL.iNet | MT2500 | version 4.8.* | Vulnerable | CVE Program (cve.org) e CISA ADP |
| GL.iNet | MT3000 | version 4.8.* | Vulnerable | CVE Program (cve.org) e CISA ADP |
| GL.iNet | MT6000 | version 4.8.* | Vulnerable | CVE Program (cve.org) e CISA ADP |
| GL.iNet | X3000 | version 4.8.* | Vulnerable | CVE Program (cve.org) e CISA ADP |
| GL.iNet | XE3000 | version 4.8.* | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 2.3 | CVSS 4.0 | Low | — | — | cna@vuldb.com via NIST National Vulnerability Database |
| 2.3 | CVSS 4.0 | Low | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 5.0 | CVSS 3.1 | Medium | 1.6 | 3.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 5.0 | CVSS 3.1 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 5.0 | CVSS 3.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 4.6 | CVSS 2.0 | Medium | 3.9 | 6.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 4.6 | CVSS 2.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L (score shown at the top: cna@vuldb.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.20%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · gl.inet/a1300, gl.inet/ax1800, gl.inet/axt1800, gl.inet/mt2500, gl.inet/mt3000, gl.inet/mt6000, gl.inet/x3000, gl.inet/x
- SSVC assessment updated
- Record published
- CVSS changed · 5.0
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-19983 GL.iNet XE3000 NAS Command Service gl_nas_sys os command injection Aug 17, 2026
- High CVE-2026-19982 GL.iNet BE9300/MT6000 Firewall-management RPC os command injection Aug 17, 2026
- High CVE-2026-19980 GL.iNet XE3000 Language Update ui.update_langs code injection Aug 17, 2026
- High CVE-2026-19981 GL.iNet XE3000 Wi-Fi Timer Power-Schedule Feature os command injection Aug 17, 2026
- High CVE-2026-19979 GL.iNet XE3000 WebDAV Service MOVE authorization Aug 17, 2026
- High CVE-2026-18787 GL.iNet AX1800 RPC Endpoint oui-rpc.lua remove_rule command injection Aug 4, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-11505 is "GL.iNet XE3000 glnassys hard-coded key", rated Medium. It affects A1300 (GL.iNet); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.0 describes technical severity. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.