# CVE-2026-18584: GL.iNet E5800/E750/X2000/X3000/XE3000/XE300 eSIM LPA API v1 improper authorization

> An attacker on the local network can bypass authorization checks in the eSIM LPA API of GL.iNet routers.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-ww63-fp7c-4c6q

## What is CVE-2026-18584?

CVE-2026-18584 is a medium-severity missing authorization vulnerability in GL.iNet E5800, published on 3 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability has been detected in GL.iNet E5800, E750, X2000, X3000, XE3000 and XE300 up to 20260707. Impacted is an unknown function of the file /sdk/v1 of the component eSIM LPA API. Such manipulation leads to improper authorization. The attack can only be initiated within the local network. The vendor was contacted early about this disclosure and confirmed the existence of the vulnerability.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-18584 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18584 is a medium-severity missing authorization vulnerability in GL.iNet E5800, published on 3 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18584 in the wild and no public exploit code.

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

## Sources

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

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