# CVE-2026-112016: Netcore NR256CN through 1.5.140116 Unauthenticated Write to Fixed Boa Staging Files

> Remote attackers can overwrite firmware update and configuration restore staging files on Netcore NR256CN routers without authentication, leading to data tampering or denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-498m-g7jx-66f7

## What is CVE-2026-112016?

CVE-2026-112016 is a medium-severity missing authorization vulnerability in Netcore NR256CN, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netcore NR256CN through 1.5.140116 contains an unauthenticated file write vulnerability in the Boa-derived /bin/boa web server that allows remote attackers to overwrite update and restore staging files. Attackers can POST to a non-existent .cgi pathname to write attacker-controlled content into /tmp/boa_temp.update or /tmp/boa_temp.para, tampering with pending firmware updates or configuration restores or causing denial of service.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-112016 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112016 is a medium-severity missing authorization vulnerability in Netcore NR256CN, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112016 in the wild and no public exploit code.

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

## Sources

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

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