# CVE-2026-92255: Netcore NR255-V 1.5.130703 Out-of-Bounds Read in filter_arp_put_file.cgi via String API Misuse

> Attackers can trigger an out-of-bounds read in the router's CGI script to expose adjacent memory contents.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-2636-fg22-863m

## What is CVE-2026-92255?

CVE-2026-92255 is a medium-severity vulnerability in Netcore NR255-V, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Netcore NR255-V version 1.5.130703 contains an out-of-bounds read vulnerability in filter_arp_put_file.cgi caused by improper use of a string handling API. Attackers can trigger an unterminated buffer over-read by exploiting this flaw in the affected component, potentially exposing adjacent memory contents.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-92255 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92255 is a medium-severity vulnerability in Netcore NR255-V, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92255 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-92255/ (Markdown: https://insights.sbomify.com/CVE-2026-92255/index.md)
```

## Sources

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

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