CVE-2026-70558

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-07. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Dinky's POST /download/uploadFromRsByLocal handler passes the caller-supplied path parameter directly to new File(path) and file.transferTo(dest) with no path validation. The route is marked @SaIgnore and /download/** is excluded from the Sa-Token interceptor, so the only guard is a header equality check against a dinkyToken value whose default (efda1551-7958-4e0f-80a8-dfd107df3e38) is hardcoded in source and shipped to every deployment. Anyone who can reach Dinky's HTTP port (8888 by default) and supplies the hardcoded token can write arbitrary files as the Dinky service account. The default Docker image runs on 8888 with no proxy or authentication and chmod 777 on /opt/dinky, so the application's own classpath, launch scripts, and static assets are writable. Demonstrated impact: overwriting /opt/dinky/config/static/index.html served attacker JavaScript to admin browsers immediately, and writing /opt/dinky/org/dinky/Dinky.class executed attacker code as the Dinky service account at the next JVM start via a classpath-shadow launched by script/bin/auto.sh. Writes are uid 9999 (flink), not root, so /etc, /root, /home, and /usr are refused. Affects Dinky v1.2.5 (the current release) and the development branch, where the code is byte-identical.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 6, 2026

Last Modified

August 31, 2026

Advisory Details (2)

Auto-updated Sep 28, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

[Security] Unauthenticated arbitrary file write via POST /download/uploadFromRsByLocal (DownloadController.uploadFromRs) leading to code execution — v1.2.5 and dev branch, CVSS 9.8 · Issue #4566 · DataLinkDC/dinky · GitHub

https://github.com/DataLinkDC/dinky/issues/4566
generic

GitHub - DataLinkDC/dinky: Dinky is a real-time data development platform based on Apache Flink, enabling agile data development, deployment and operation. · GitHub

https://github.com/DataLinkDC/dinky

Vendor Advisories for CVE-2026-70558(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 146× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 354 total refreshes for this CVE.

  1. 2026-10-05 18:37 UTCEG score recompute
  2. 2026-10-05 18:37 UTCGHSA enrichment
  3. 2026-10-05 17:43 UTCEPSS rescore
  4. 2026-10-05 08:23 UTCEG score recompute
  5. 2026-10-05 08:23 UTCGHSA enrichment
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCGHSA enrichment
  8. 2026-10-04 14:44 UTCGHSA enrichment
  9. 2026-10-04 10:19 UTCGHSA enrichment
  10. 2026-10-04 05:48 UTCEG score recompute
  11. 2026-10-04 05:48 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 01:03 UTCEG score recompute
  14. 2026-10-03 01:03 UTCGHSA enrichment
  15. 2026-10-02 17:56 UTCEPSS rescore
  16. 2026-10-02 16:32 UTCGHSA enrichment
  17. 2026-10-02 09:38 UTCEG score recompute
  18. 2026-10-02 09:38 UTCGHSA enrichment
  19. 2026-10-01 19:50 UTCEPSS rescore
  20. 2026-10-01 12:11 UTCGHSA enrichment
  21. 2026-10-01 07:46 UTCGHSA enrichment
  22. 2026-10-01 03:23 UTCGHSA enrichment
  23. 2026-09-30 23:01 UTCEG score recompute
  24. 2026-09-30 23:00 UTCGHSA enrichment
  25. 2026-09-30 15:03 UTCEPSS rescore
Show 75 more
  1. 2026-09-29 05:53 UTCEG score recompute
  2. 2026-09-29 05:53 UTCGHSA enrichment
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 12:50 UTCGHSA enrichment
  5. 2026-09-28 06:52 UTCGHSA enrichment
  6. 2026-09-28 02:28 UTCGHSA enrichment
  7. 2026-09-27 17:28 UTCEG score recompute
  8. 2026-09-27 17:28 UTCGHSA enrichment
  9. 2026-09-27 13:48 UTCEPSS rescore
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-25 08:46 UTCGHSA enrichment
  12. 2026-09-25 04:21 UTCEG score recompute
  13. 2026-09-25 04:21 UTCGHSA enrichment
  14. 2026-09-24 10:26 UTCGHSA enrichment
  15. 2026-09-24 06:03 UTCGHSA enrichment
  16. 2026-09-24 01:40 UTCGHSA enrichment
  17. 2026-09-23 21:17 UTCEG score recompute
  18. 2026-09-23 21:17 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 14:51 UTCGHSA enrichment
  21. 2026-09-23 10:29 UTCGHSA enrichment
  22. 2026-09-23 06:06 UTCGHSA enrichment
  23. 2026-09-23 01:43 UTCGHSA enrichment
  24. 2026-09-22 21:20 UTCEG score recompute
  25. 2026-09-22 21:20 UTCGHSA enrichment
  26. 2026-09-22 15:46 UTCGHSA enrichment
  27. 2026-09-22 11:24 UTCGHSA enrichment
  28. 2026-09-22 05:23 UTCGHSA enrichment
  29. 2026-09-22 01:01 UTCEG score recompute
  30. 2026-09-22 01:01 UTCGHSA enrichment
  31. 2026-09-21 21:09 UTCEPSS rescore
  32. 2026-09-21 12:46 UTCGHSA enrichment
  33. 2026-09-20 20:35 UTCEG score recompute
  34. 2026-09-20 20:35 UTCGHSA enrichment
  35. 2026-09-20 20:16 UTCEPSS rescore
  36. 2026-09-20 10:57 UTCGHSA enrichment
  37. 2026-09-20 02:19 UTCGHSA enrichment
  38. 2026-09-19 21:57 UTCGHSA enrichment
  39. 2026-09-19 17:33 UTCEG score recompute
  40. 2026-09-19 17:33 UTCGHSA enrichment
  41. 2026-09-19 12:59 UTCGHSA enrichment
  42. 2026-09-19 08:27 UTCGHSA enrichment
  43. 2026-09-19 04:04 UTCGHSA enrichment
  44. 2026-09-18 23:40 UTCEG score recompute
  45. 2026-09-18 23:40 UTCGHSA enrichment
  46. 2026-09-18 19:28 UTCEPSS rescore
  47. 2026-09-18 19:12 UTCGHSA enrichment
  48. 2026-09-18 14:44 UTCGHSA enrichment
  49. 2026-09-18 09:43 UTCGHSA enrichment
  50. 2026-09-18 05:20 UTCGHSA enrichment
  51. 2026-09-18 00:57 UTCEG score recompute
  52. 2026-09-18 00:57 UTCGHSA enrichment
  53. 2026-09-17 15:14 UTCGHSA enrichment
  54. 2026-09-17 09:43 UTCGHSA enrichment
  55. 2026-09-17 05:20 UTCGHSA enrichment
  56. 2026-09-17 00:57 UTCEG score recompute
  57. 2026-09-17 00:57 UTCGHSA enrichment
  58. 2026-09-16 14:08 UTCEPSS rescore
  59. 2026-09-16 11:46 UTCGHSA enrichment
  60. 2026-09-16 07:23 UTCEG score recompute
  61. 2026-09-16 07:23 UTCGHSA enrichment
  62. 2026-09-16 05:15 UTCEPSS rescore
  63. 2026-09-16 02:58 UTCGHSA enrichment
  64. 2026-09-15 14:24 UTCGHSA enrichment
  65. 2026-09-15 06:44 UTCEG score recompute
  66. 2026-09-15 06:44 UTCGHSA enrichment
  67. 2026-09-15 03:12 UTCEPSS rescore
  68. 2026-09-15 01:08 UTCGHSA enrichment
  69. 2026-09-14 14:03 UTCGHSA enrichment
  70. 2026-09-14 09:15 UTCGHSA enrichment
  71. 2026-09-14 04:53 UTCGHSA enrichment
  72. 2026-09-14 00:29 UTCGHSA enrichment
  73. 2026-09-13 20:06 UTCEG score recompute
  74. 2026-09-13 20:06 UTCGHSA enrichment
  75. 2026-09-13 15:43 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-70558?
CVE-2026-70558 is a critical vulnerability published on August 6, 2026. Dinky's POST /download/uploadFromRsByLocal handler passes the caller-supplied path parameter directly to new File(path) and file.transferTo(dest) with no path validation. The route is marked @SaIgnore and /download/ is excluded from the Sa-Token interceptor, so the only guard is a header equality…
When was CVE-2026-70558 disclosed?
CVE-2026-70558 was first published on August 6, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70558 actively exploited?
CVE-2026-70558 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70558?
CVE-2026-70558 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-70558?
No fix for CVE-2026-70558 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-70558 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-70558

Explore →

Is Your Infrastructure Affected by CVE-2026-70558?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs