Skip to content
High-Risk API Key Vulnerability in Skyline DataMiner BrokerGateway

High-Risk API Key Vulnerability in Skyline DataMiner BrokerGateway

First seen 6 Nov 2026, 22:46 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 6, 2026 at 22:47 UTC
  • •CVE-2026-89017 allows unauthenticated access to sensitive API keys.
  • •High risk for organizations with exposed DataMiner BrokerGateway deployments.
  • •Immediate upgrade to patched versions is recommended to mitigate risks.

Skyline DataMiner BrokerGateway has an embedded API key vulnerability (CVE-2026-89017) that allows unauthenticated attackers to retrieve the installation-specific BrokerGateway key. This vulnerability enables attackers to access the DataMinerUser.creds NATS credential and gain trusted message-bus access via TCP port 4222 without prior credentials. The flaw affects organizations with internet-accessible network-management platforms, particularly those where the broker is reachable from user or partner networks. The vulnerability has been assigned a CVSS score of 8.7, indicating high risk. It was fixed in versions 10.6.9 CU1, 10.6.0 CU7, 10.5.0 CU19, and 10.4.0 CU22. There is currently no confirmed active exploitation or KEV status provided, but the potential for unauthorized access to operational data raises concerns about data confidentiality. Organizations are advised to upgrade promptly and restrict access to the gateway and broker.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated 17h ago How this analysis works

Timeline

2026-11-06
CVE-2026-89017 published
Skyline Communications disclosed a critical API key vulnerability affecting DataMiner BrokerGateway.
Redpacketsecurity

More articles in this cluster (3)

Following this threat?

Track Skyline Communications and CVE-2026-89017 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (5)

1 / 3

Common questions

What versions are affected by CVE-2026-89017?
Versions 10.6.9 CU1, 10.6.0 CU7, 10.5.0 CU19, and 10.4.0 CU22 are fixed; earlier versions are vulnerable.
Is there any active exploitation of this vulnerability?
Currently, there is no confirmed active exploitation reported for CVE-2026-89017.
What should organizations do to protect themselves?
Organizations should upgrade to the latest patched versions and restrict access to the BrokerGateway.