# CVE-2026-108907: Netcore NR268 CGI Execution user_ok improper authentication

> Remote attackers can bypass authentication in the Netcore NR268 router's CGI execution component due to improper validation in the user_ok function.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-382f-xr7m-w8hq

## What is CVE-2026-108907?

CVE-2026-108907 is a critical authentication bypass vulnerability in Netcore NR268, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in Netcore NR268 1.7.121109. Affected is the function user_ok of the component CGI Execution. This manipulation causes improper authentication. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-108907 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108907 is a critical authentication bypass vulnerability in Netcore NR268, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108907 exists.

Affected product: Netcore NR268. 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-108907/ (Markdown: https://insights.sbomify.com/CVE-2026-108907/index.md)
```

## Sources

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

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