VulnerabilityPublished 29 Sep 2026Updated 1 Oct 2026

CVE-2026-102241: Netcore NAP930 · Use of Hard-coded Cryptographic Key

Affects Netcore NAP930Source CVE Database V5

Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS

0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: Proof of concept is public or traded
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-01.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 29 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by VulDB
28 Sep 202618:38 UTC, 8 hours before disclosure
CVE published
on cve.org
29 Sep 202602:15 UTC, t = 0
CISA SSVC assessment
proof of concept public
1 Oct 202615:30 UTC, 2 days after disclosure
In Threat Radar
record ingested
26 Oct 202608:08 UTC, 27 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
NetcoreNAP930	Affected =0.1.241010.141410	Fixed in–

CPE configurations (1)

cpe:2.3:a:netcore:nap930:*:*:*:*:*:*:*:*

AI-suggested

Since the vendor has not responded or provided a fix, users should consider mitigating risk by restricting network access to the affected device, disabling backup/restore features if possible, or isolating the device until a fix is available. Monitor vendor channels for any future updates or patches.

Description

CVE-2026-102241 is a medium severity vulnerability in Netcore NAP930 version 0.1.241010.141410. It involves the use of a hard-coded cryptographic key in the Backup/Restore component, specifically in the file /lib/functions/backup_common.sh. This flaw allows remote attackers to exploit the hard-coded key, potentially compromising cryptographic protections. The vulnerability has been publicly disclosed with exploit details available, but the vendor has not responded or provided a fix.

Impact

The use of a hard-coded cryptographic key weakens the cryptographic security of the affected component, potentially allowing remote attackers to decrypt or manipulate backup data protected by this key. This compromises confidentiality and integrity of backup/restore operations. The CVSS 4.0 base score is 5.1 (medium), reflecting network attack vector, low complexity, and no user interaction required, but requiring high privileges.

Summary

The vulnerability CVE-2026-102241 affects Netcore NAP930 version 0.1.241010.141410. It is caused by the use of a hard-coded cryptographic key in the Backup/Restore component's script /lib/functions/backup_common.sh. Manipulation of the argument aes_pass leads to this insecure use of a fixed key. The vulnerability is remotely exploitable and has been publicly disclosed. No vendor response or patch has been provided as of the publication date.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

CPE configurations (1)

Description

AI analysisMachine-generated, updated 3 Nov 2026, 05:14 UTC

Technical details

References

Community reviews

Related threats