VulnerabilityPublished 6 Nov 2026

CVE-2026-89017: Skyline Communications DataMiner · Use of Hard-coded Credentials

Affects Skyline Communications DataMinerSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.7 High · fixed in 10.6.9 : patch Skyline Communications DataMiner soon.

Data as of 6 Nov 2026, 18:10 UTC

CVSS 4.0 base score

8.7High

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	8.7
CNA (VulnCheck)	CVSS 3.1	7.5

Patch: Available – fixed in 10.6.9

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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 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
Skyline CommunicationsDataMiner	Affected 10.4.0 – 10.6.9 4 affected builds	Fixed in–

AI-suggested

Apply the official fixes provided by Skyline Communications in DataMiner versions 10.6.9 CU1, 10.6.0 CU7, 10.5.0 CU19, and 10.4.0 CU22. Upgrading to these versions or later will remediate the vulnerability. No other mitigations are indicated by the vendor advisory.

Description

CVE-2026-89017 is a high-severity vulnerability in Skyline Communications DataMiner BrokerGateway involving an embedded API key. This flaw allows unauthenticated attackers to retrieve the installation-specific BrokerGateway key even when pairing mode is disabled. With this key, attackers can access the unrestricted DataMinerUser.creds NATS credential and gain trusted message-bus access via TCP port 4222 without needing prior credentials. The issue is fixed in DataMiner versions 10.6.9 CU1, 10.6.0 CU7, 10.5.0 CU19, and 10.4.0 CU22.

Impact

An unauthenticated attacker can retrieve an installation-specific API key and use it to gain unrestricted access to the DataMiner message bus, potentially allowing unauthorized message publishing or subscription with trusted credentials. This compromises the integrity and confidentiality of the message bus communications within the DataMiner environment.

Summary

The vulnerability in Skyline DataMiner BrokerGateway is due to the use of a hard-coded embedded API key that can be retrieved by unauthenticated attackers regardless of pairing mode status. Exploiting this allows attackers to obtain the BrokerGateway key, which in turn grants access to the DataMinerUser.creds NATS credential. This credential provides trusted access to the message bus over TCP port 4222 without requiring any prior authentication. This could enable attackers to interact with the DataMiner message bus with high privileges. The vendor has addressed this vulnerability with fixes released in specific cumulative updates for DataMiner versions 10.6.9, 10.6.0, 10.5.0, and 10.4.0.

References

Community reviews

Loading reviews…