CVE Alert: CVE-2026-89017 – Skyline Communications

Skyline DataMiner BrokerGateway contains an embedded API key vulnerability that allows unauthenticated attackers to retrieve the installation-specific BrokerGateway key even while pairing mode is disabled. Attackers can use the retrieved key to obtain the unrestricted DataMinerUser.creds NATS credential and gain trusted message-bus access via TCP port 4222 without any prior DataMiner credentials. Fixed in DataMiner 10.6.9 CU1, 10.6.0 CU7, 10.5.0 CU19, and 10.4.0 CU22.

**Risk verdict:** High risk for exposed deployments; KEV and SSVC exploitation status are not provided, so active exploitation and the need for emergency response cannot be confirmed.

**Why this matters:** An unauthorised foothold in a trusted messaging layer could expose operational data and secrets, supporting reconnaissance or follow-on attacks. The assessed impact is primarily data confidentiality; there is no supplied basis to assume direct service disruption or data modification.

**Most likely attack path:** An attacker needs network reachability to the gateway, but no account, user action or special conditions. Access to the message bus could provide a route to discover connected services or credentials, although impact beyond that trust boundary is not established.

**Who is most exposed:** Organisations running internet-accessible or broadly reachable network-management platforms, particularly where the broker is reachable from user or partner networks. Internal-only deployments remain at risk if an attacker has already gained network access.

Review gateway requests and broker authentication logs for unexpected clients or access without normal pairing.

Investigate unusual connections to TCP 4222, especially from untrusted or user subnets.

Alert on unexpected retrieval or use of broker credentials and new message-bus identities.

Correlate suspicious broker activity with gateway and network-flow records.

Mitigation and prioritisation:

Upgrade promptly to the vendor’s fixed maintenance release for the installed branch.

Restrict gateway and broker access to explicitly required hosts and network segments; do not rely on pairing mode alone.

Review and rotate exposed broker credentials where feasible, then check for unauthorised clients.

Validate branch and build levels before change; test integrations in staging and monitor broker connectivity after deployment.

Obtain KEV, SSVC and EPSS status before final prioritisation; these indicators were not supplied.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.