Skip to main content

GL.iNet Routers CVE-2026-11505

| EUVDEUVD-2026-35040 LOW
Use of Hard-coded Cryptographic Key (CWE-321)
2026-06-08 VulDB GHSA-2r8p-5hq4-h3r4
2.3
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain GL.iNet 4.8.x firmware image
  2. Delivery
    Reverse engineer glnassys binary to extract hard-coded authentication token
  3. Exploit
    Identify target router running affected firmware
  4. Execution
    Craft authenticated request using static token
  5. Persist
    Issue unauthorized commands to NAS subsystem
  6. Impact
    Access or manipulate NAS data/configuration

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
Exploitation Conditions

The glnassys (GL.iNet NAS system) component must be active on the target device - this feature is present on affected models but may not be in use if no NAS functionality is configured. The CVSS vector PR:L confirms that some level of existing access (low privilege) is required; fully unauthenticated exploitation from an anonymous remote position is not indicated. The AC:H rating confirms that exploitation requires significant technical effort, likely including firmware extraction and binary reverse engineering to obtain the hard-coded token. The attack is limited to firmware version 4.8.x specifically - devices already upgraded to 4.9.0 are not affected. Devices where the NAS feature is disabled or unconfigured have reduced exposure, though the hard-coded key may still exist in the firmware image.

Impact

The CVSS 4.0 score of 2.3 is notably low and reflects several limiting factors: AC:H (high attack complexity, meaning exploitation is technically difficult and not trivially automatable), PR:L (low privileges required - the attacker must already have some level of access, not a fully unauthenticated attack), and impact constrained to VC:L/VI:L/VA:L with no lateral scope change (SC:N/SI:N/SA:N). No KEV listing exists, confirming no observed active exploitation at time of analysis. No EPSS score was provided in the input data, so exploitation probability cannot be quantified. The GitHub advisory title references 'unauthorized command execution' as the potential impact, which is more severe than the 'Information Disclosure' tag alone suggests - this internal discrepancy between the tag and the advisory title warrants attention. The real-world risk is moderate for environments where the NAS feature is actively used, but the high complexity requirement and need for prior low-level access meaningfully limits opportunistic mass exploitation.

Exploit ScenarioDerived

A low-privileged attacker with network access to an affected GL.iNet router running firmware 4.8.x could extract the hard-coded authentication token from the glnassys binary (via firmware download and reverse engineering, which is the source of the AC:H rating), then craft authenticated API requests to the NAS management subsystem using the static token. With this access, the attacker could issue unauthorized commands to the NAS component, potentially reading stored files or manipulating NAS configuration. The public GL.iNet GitHub advisory document provides sufficient detail that a motivated attacker could develop a targeted exploit.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 08, 2026

Hard-coded cryptographic key exposure in the glnassys (GL.iNet NAS system) component across eight GL.iNet router models running firmware 4.8.x enables a low-privileged remote attacker to exploit a static authentication token and potentially execute unauthorized commands against the NAS subsystem. The vulnerability is rooted in CWE-321 (Use of Hard-coded Cryptographic Key), where the firmware embeds a fixed authentication secret that cannot be rotated by users or administrators. No public exploit identified at time of analysis, and the vendor has released firmware 4.9.0 as a fix.

RemediationAI

Upgrade all affected GL.iNet router models to firmware version 4.9.0, which the vendor has confirmed mitigates this issue. A sysupgrade firmware image for the AX1800 platform is directly referenced at https://cloud-static-test.gl-inet.cn/security/openwrt-ipq60xx-glinet_ax1800-squashfs-sysupgrade.tar; users of other affected models (A1300, AXT1800, MT2500, MT3000, MT6000, X3000, XE3000) should obtain the corresponding 4.9.0 images from GL.iNet's official firmware portal. As a compensating control prior to patching, administrators should disable the NAS/glnassys feature entirely via the router's admin panel if NAS functionality is not required, which removes the attack surface for this component. Additionally, restrict management interface access to trusted VLANs or local networks only, reducing the network exposure of the glnassys service. Note that disabling NAS will render attached USB storage sharing non-functional.

Affected VersionsENISA

MT6000 4.8.*
AX1800 4.8.*
X3000 4.8.*
XE3000 4.8.*
MT2500 4.8.*
A1300 4.8.*
MT3000 4.8.*
AXT1800 4.8.*

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is glnassys, GL.iNet's NAS (Network Attached Storage) management subsystem embedded in the OpenWrt-based firmware across multiple router product lines. CWE-321 describes the use of a hard-coded cryptographic key - in this case, the GitHub advisory title reveals the key is a default authentication token embedded in the gl-nas-sys binary. Because this token is static across all affected devices, any attacker who reverse-engineers or discovers it can impersonate a legitimate authenticated session to the NAS management interface. The affected CPE strings (cpe:2.3:a:gl.inet:a1300, ax1800, axt1800, mt2500, mt3000, mt6000, x3000, xe3000) cover eight distinct router models all running firmware version 4.8.x on OpenWrt/ipq60xx and related platforms.

Know when A1300 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.3 LOW
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

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
High
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Severity Changed
Jun 08, 2026 - 12:22 NVD
MEDIUM LOW
CVSS changed
Jun 08, 2026 - 12:22 NVD
5.0 (MEDIUM) 2.3 (LOW)

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.0%
Top 87% exploitable
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

12
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +12
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy