CVE-2026-129866 · Other
NO FIX YET
Dinky through 1.2.5 has a missing authorization check in its ClusterConfigurationController. Any logged-in user without cluster configuration permission can call the list and listAll endpoints and read full deployment settings for every cluster in their tenant.
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, a platform for Apache Flink, where ordinary logged-in users share an instance with others. The flaw exposes cluster configuration data, so exposure depends on whether accounts without cluster configuration rights exist. unknown whether a fixed version is available in the sources, though linked patch references exist.
Not affected if no-untrusted-accounts, single-user-instance
Who cares apache-flink, dinky, self-hosted
1.2.5 or earlier in the product rangesNo fix yet, per the sources.
Dinky through 1.2.5 contains a missing authorization vulnerability in ClusterConfigurationController that allows authenticated users without cluster configuration permissions to list Flink cluster configurations. Attackers can query the /api/clusterConfiguration/list and listAll endpoints to retrieve full configJson deployment settings for every cluster in their tenant.
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.