# CVE-2026-70559: Dinky Unauthenticated System Configuration and Credential Disclosure via GET /api/sysConfig/getAll

> Unauthenticated attackers can access system configuration endpoints to steal cleartext credentials and bypass token-based file upload protections.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-83jg-x5rh-3x8c, GHSA-c48m-x2xw-32rj

## What is CVE-2026-70559?

CVE-2026-70559 is a high-severity missing authorization vulnerability in DataLinkDC Dinky, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dinky's SysConfigController.getAll() handler for GET /api/sysConfig/getAll carries a method-level @SaIgnore annotation that short-circuits the class-level @SaCheckLogin, so the Sa-Token interceptor lets the request through with no session or role check. Any remote unauthenticated caller who can reach the Dinky HTTP port (8888 by default) receives the full live system configuration (54 entries on a stock v1.2.5 install) with one parameterless GET. Only one credential field (sys.maven.settings.repositoryPassword) has a desensitization handler wired; the other credential-bearing fields (sys.env.settings.dinkyToken, sys.ldap.settings.userPassword, sys.resource.settings.oss.accessKey and secretKey, and sys.dolphinscheduler.settings.token) return in cleartext. A bare install leaks the shipped defaults, including the hardcoded dinkyToken efda1551-7958-4e0f-80a8-dfd107df3e38 and minioadmin/minioadmin OSS keys; once an operator configures LDAP, object storage, or DolphinScheduler through the Settings Center, those live third-party credentials leak from the same endpoint. Because dinkyToken is the sole gate on the sibling POST /download/uploadFromRsByLocal arbitrary file write, this disclosure defeats token rotation as a mitigation for that vulnerability. Affects Dinky v1.2.5 (the current release, 2025-11-05) and the development branch (dev HEAD 63b5a5a), where the affected code is byte-identical.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-70559?


## How do I fix CVE-2026-70559?

No fix has been published for CVE-2026-70559 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70559 being exploited?

There is no known exploitation of CVE-2026-70559 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-70559 (github_poc): https://github.com/codeb0ssx/CVE-2026-70559-PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70559 and fix it if it is affected.

What it is: CVE-2026-70559 is a high-severity missing authorization vulnerability in DataLinkDC Dinky, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70559 in the wild and no public exploit code.

Affected product: DataLinkDC Dinky. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-70559/ (Markdown: https://insights.sbomify.com/CVE-2026-70559/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70559
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70559
- OSV: https://osv.dev/vulnerability/CVE-2026-70559

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-70559/
Summaries are generated and may contain mistakes; the official description above is the record.