CVE-2026-70559
Unauthenticated GET leaks Dinky system config and secrets enabling arbitrary file write/RCE.
Is CVE-2026-70559 being exploited?
Not confirmed. CVE-2026-70559 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-70559?
CVE-2026-70559 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-70559?
Yes. A fix has been recorded for CVE-2026-70559. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70559 affect?
CVE-2026-70559 affects Dinky v1.2.5, Dinky dev HEAD (63b5a5a), Default HTTP port 8888 (exposed instances). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70559?
Block/limit access to port 8888, rotate exposed credentials/keys, and apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote info disclosure of cleartext credentials and dinkyToken; token enables arbitrary file write (leading to RCE) and access to third-party resources.
Immediate action required
- affected<= 1.2.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.