Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-70559 – Unauthenticated System Configuration & Credential Disclosure – Dinky through 1.2.5

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-70559 is a missing-authentication vulnerability (CWE-306) in DataLinkDC Dinky, a real-time data development platform based on Apache Flink. An unauthenticated remote attacker can retrieve the complete system configuration — including cleartext credentials — through an exposed API endpoint. The issue is rated High severity (CVSS v3.1 base score 7.5).

Technical details

  • Root cause: The GET /api/sysConfig/getAll endpoint carries a method-level @SaIgnore annotation that overrides the class-level login check, so the request is served without any session or role validation.
  • Trigger conditions: A single parameterless, unauthenticated HTTP GET request to the endpoint on a reachable Dinky instance.
  • Attack vector: Network — no privileges and no user interaction required.
  • Impact: Disclosure of the full live system configuration. Multiple credential fields are returned in cleartext, including sys.env.settings.dinkyToken, sys.ldap.settings.userPassword, sys.resource.settings.oss.accessKey, sys.resource.settings.oss.secretKey, and sys.dolphinscheduler.settings.token. Exposed secrets can enable access to connected LDAP, object-storage, and scheduling systems.

Affected software

  • DataLinkDC Dinky: all versions from 0 through 1.2.5.

Severity

  • CVSS v3.1 base score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • The CVE record also lists a CVSS v4.0 score of 8.7 (High) — 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

Mitigation and recommended actions

  • Immediate: No fixed version is identified in the CVE record or vendor advisory at time of writing. Monitor the DataLinkDC Dinky GitHub advisory (GHSA-c48m-x2xw-32rj) and releases page, and upgrade as soon as a patched release is published.
  • If no patch: Restrict network access to the Dinky management interface so it is not reachable from untrusted networks; place it behind an authenticating reverse proxy or VPN and enforce IP allow-listing. Rotate any credentials that may have been exposed via the endpoint (tokens, LDAP passwords, object-storage keys, and scheduler tokens).

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge