CVE-2026-129865 · Package
NO FIX YET · SEE WHAT TO DO
Dinky's DataSourceController.testConnect endpoint skips the authorization check, so any authenticated user can open JDBC connections to hosts of their choosing. An attacker can probe internal hosts and ports through driver errors, and a crafted MySQL JDBC URL with local-infile can make the Dinky host read local files.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running Dinky with user accounts that are not fully trusted are exposed, since any authenticated user can reach the test-connection endpoint. Deployments where only administrators can log in can treat this as lower risk but should still upgrade.
Not affected if auth-required-admin-only, single-trusted-user
Who cares dinky, java, jdbc, self-hosted
1.2.5 are affected.1.2.5 (the sources do not name the exact fixed version; see the linked patch).Dinky through 1.2.5 contains a missing authorization vulnerability in DataSourceController.testConnect that allows any authenticated user to open arbitrary JDBC connections by supplying caller-controlled connection settings. Attackers can probe internal hosts and ports via returned driver errors, or supply a MySQL JDBC URL enabling local-infile against a malicious server to read files from the Dinky host.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.