CVE-2026-70558
Hardcoded-token file upload in Dinky allows arbitrary file write and RCE on restart
Is CVE-2026-70558 being exploited?
Not confirmed. CVE-2026-70558 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.60% probability of exploitation in the next 30 days.
How severe is CVE-2026-70558?
CVE-2026-70558 is rated Critical with a CVSS score of 9.3. 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-70558?
Yes. A fix has been recorded for CVE-2026-70558. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70558 affect?
CVE-2026-70558 affects Dinky v1.2.5, Dinky development branch, Default Dinky Docker image (port 8888). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70558?
Restrict port 8888, override/remove default token, replace default image, apply vendor patch when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary file write as Dinky service (uid 9999) via hardcoded token; can serve malicious assets and achieve RCE on JVM restart.
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.