NR268: Missing Support for Integrity Check
CVE-2026-76853 is a high-severity missing support for integrity check vulnerability in NR268 from Netcore, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected NR268 versions: 1.7.121109. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.26% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of NR268 you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.2 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 8.1 | High | CNA (vulncheck.com) |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Support for Integrity Check
The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.
How developers prevent this class of flaw
- Add an appropriately sized checksum to the protocol, ensuring that data received may be simply validated before it is parsed and used.
- Ensure that the checksums present in the protocol design are properly implemented and added to each message before it is sent.
More Missing Support for Integrity Check vulnerabilities (CWE-353)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in NR268
- 9.9 Critical severity
- 10.0 Critical severity
- 7.2 High severity
- 8.8 High severity
Recent Missing Support for Integrity Check vulnerabilities
- 8.4 High severity
- 7.5 High severity
- 8.7 High severity
- 7.1 High severity
- 9.1 Critical severity
- 7.3 High severity
Spotted an error? Tell us.