# CVE-2026-76853: Netcore NR268 1.7.121109 Security Check Bypass in parame_put_file.cgi

> Attackers can bypass security checks in the restore archive handling of Netcore NR268 routers, potentially allowing unauthorized configuration changes.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/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:** 16 Sep 2026
- **Also known as:** GHSA-6mhv-w69c-76fg

## What is CVE-2026-76853?

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

### Official description

Netcore NR268 firmware version 1.7.121109 contains a security check bypass vulnerability in the parame_put_file.cgi restore archive prefix validation. Attackers can exploit the flawed prefix check in put_parame_file_cgi.c to bypass restricted restore archive handling.

Weakness: CWE-353 (Missing Support for Integrity Check)

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


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

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

## Is CVE-2026-76853 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76853 is a high-severity vulnerability in Netcore NR268, 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-76853 in the wild and no public exploit code.

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-76853/ (Markdown: https://insights.sbomify.com/CVE-2026-76853/index.md)
```

## Sources

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

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