# CVE-2025-67090: Security feature bypass in n/a

> An unauthenticated attacker on the local network can perform unlimited password attempts against the admin interface due to missing rate limiting.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **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:** 8 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-jjmx-7vpw-fcc5

## What is CVE-2025-67090?

CVE-2025-67090 is a medium-severity vulnerability in n/a, published on 8 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The LuCI web interface on Gl Inet GL.Inet AX1800 Version 4.6.4 & 4.6.8 are vulnerable. Fix available in version 4.8.2 GL.Inet AX1800 Version 4.6.4 & 4.6.8 lacks rate limiting or account lockout mechanisms on the authentication endpoint (`/cgi-bin/luci`). An unauthenticated attacker on the local network can perform unlimited password attempts against the admin interface.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2025-67090?

It affects 1 product.


Products: Gl-Inet Ax1800 Firmware.

## How do I fix CVE-2025-67090?

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

## Is CVE-2025-67090 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67090 exists.

## Other vulnerabilities in n/a

- [CVE-2025-67091](https://insights.sbomify.com/CVE-2025-67091/): Race condition in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67090 and fix it if it is affected.

What it is: CVE-2025-67090 is a medium-severity vulnerability in n/a, published on 8 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67090 exists.

Affected product: n/a. 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-2025-67090/ (Markdown: https://insights.sbomify.com/CVE-2025-67090/index.md)
```

## Sources

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

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