Dinky's vulnerability footprint centers on a single product and reflects a pattern of authentication and access-control weaknesses, including improper authentication mechanisms, missing authentication for critical functions, path-traversal conditions, and server-side request forgery. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Dinky over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-3053CRITICAL A vulnerability was determined in DataLinkDC dinky up to 1.2.5. This affects the function addInterceptors of the file dinky-admin/src/main/java/org/dinky/configure/AppConfig.java o | Feb 24, 2026 | 9.8 | 29 | NO | NO |
CVE-2026-3052HIGH A vulnerability was found in DataLinkDC dinky up to 1.2.5. The impacted element is the function proxyUba of the file dinky-admin/src/main/java/org/dinky/controller/FlinkProxyContro | Feb 24, 2026 | 7.7 | 26 | NO | NO |
CVE-2026-3051HIGH A vulnerability has been found in DataLinkDC dinky up to 1.2.5. The affected element is the function getProjectDir of the file dinky-admin/src/main/java/org/dinky/utils/GitReposito | Feb 24, 2026 | 7.6 | 25 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Dinky.
Media articles that mention a CVE ID that affects a product developed by Dinky — matched by CVE ID, not by vendor name.