CVE-2026-129866
Dinky through 1.2.5 contains a missing authorization vulnerability in ClusterConfigurationController that allows authenticated users without
CVSS
4.3
Medium
EPSS
—
KEV
—
Exploit Today
—
0-100
Published: Nov 16, 2026 · Last modified: Nov 16, 2026 · CWE-862
Not enough EPSS history yet.
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.
- github.comhttps://github.com/DataLinkDC/dinky/blob/v1.2.5/dinky-admin/src/main/java/org/dinky/controller/ClusterConfigurationController.java#L103-L125
- github.comhttps://github.com/DataLinkDC/dinky/commit/856d9df7e0e4ddc394f16b4f33c7574ef1e9f4e6
- github.comhttps://github.com/DataLinkDC/dinky/commit/a6432b189b28c6b83e237f66553305a236109cb0
- github.comhttps://github.com/DataLinkDC/dinky/pull/4621
- hackmd.iohttps://hackmd.io/@hieund/dinky-datasource-testconnect-missing-authz-jdbc-ssrf-file-read
- www.vulncheck.comhttps://www.vulncheck.com/advisories/dinky-through-1.2.5-missing-authorization-via-clusterconfiguration-list-endpoints
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-911134.3 MED—
———Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a CMS user who can edit a record through a GridField detail form can submit a user-controlled ClassName value to change the record into an unrelated class without the create and edit permission checks required for that target class. This permits an unauthorized record type change outside the GridField's intended model hierarchy. This issue is fixed in version 6.2.13.5hCVE-2026-889894.3 MED—
———Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a CMS user who can edit records through a GridField detail form can send a direct save request that creates a new record even when the user does not have permission to create that record type. The server-side save path checks edit access but does not enforce the required create permission before persistence. This issue is fixed in version 6.2.13.6hCVE-2026-1136316.5 MED—
———Incorrect authorization in the sendForm RPC handler and Session JWT reconnect handling in ONLYOFFICE Docs (Document Server) 9.4.0-129 on the official onlyoffice/documentserver container allows an authenticated view-only user to export a reconstructed copy of a document, including content the viewer never displayed such as custom XML, custom document properties and field instruction text, even when download and form-filling are disabled. The attacker reconnects with a valid Session JWT while substituting an attacker-controlled callback URL, which the Session JWT does not bind, then invokes sendForm over RPC, causing DocumentServer to send the reconstructed DOCX to that URL.6hCVE-2026-1298865.3 MED—
———thirdweb Dashboard through commit 940b3745 contains a missing authorization vulnerability in revalidatePathAction and revalidateCacheTagAction server actions in revalidate.ts. Unauthenticated attackers can use action identifiers exposed in the client bundle to send POST requests that purge cached pages and data, forcing repeated regeneration and degrading performance.8hCVE-2026-1298715.3 MED—
———Rocboss paopao-ce through 0.6.0-alpha.3 contains a payment bypass vulnerability that allows unauthenticated attackers to obtain paid attachments by reading storage URLs from the GET /v1/post endpoint. Attackers can download the paid file directly from the unauthenticated LocalOSS /oss static route, whose signed URL expired parameter is never checked.6hCVE-2026-74763——
———Authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always enforced in some class or interface hierarchies.
Annotations declared on an interface were not enforced when using the shiro-guice, shiro-aspectj, shiro-cdi or shiro-jakarta-ee modules.
In addition, annotations declared on a class or a superclass were not always enforced when using shiro-guice or shiro-aspectj, allowing an unauthorized caller to invoke methods that should be protected.
This issue affects all Apache Shiro versions through 3.0.1, with impact depending on module and where annotations are declared.
Mitigation: Upgrade to version 3.0.2 or later, which fixes the issue. The annotation closest to the invoked method now takes precedence.
Alternatively, declare authorization annotations directly on each protected implementing method.8h