# CVE-2026-76865: Netcore NR255-V 1.5.130703 NULL Pointer Dereference via Unchecked atoi() in QoS Setter Handlers

> An attacker can cause a denial of service on Netcore NR255-V routers by sending crafted input to QoS setter handlers, triggering a null pointer dereference.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-3f5g-mqj3-72gq

## What is CVE-2026-76865?

CVE-2026-76865 is a medium-severity vulnerability in Netcore NR255-V, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Netcore NR255-V version 1.5.130703 contains a null pointer dereference vulnerability in the QoS setter CGI handlers filter_conn_del_cgi.c and gre_prio_set_cgi.c due to unchecked atoi() results. An attacker can trigger the flaw by supplying crafted input to these handlers, causing a denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2026-76865 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76865 is a medium-severity vulnerability in Netcore NR255-V, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76865 in the wild and no public exploit code.

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

## Sources

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

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