CVE-2026-11500

MediumCVSS 5.0

Published: 08/06/2026(UTC)Updated: 23/07/2026(UTC)Translated: 25/07/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.28%

20th percentile - higher than 20% of all known CVEs

Summary

In Weaviate up to version 1.37.7, a vulnerability was found in the validateConfig function in usecases/auth/authentication/apikey/client.go. Manipulation of the StaticApiKey argument leads to authorization bypass. The attack is remote but difficult. The exploit is publicly available. A fix is available in version 1.38.0-rc.0.

Risk Assessment

The risk involves a remote attacker being able to bypass authorization mechanisms, potentially leading to unauthorized access to data and functions in Weaviate.

Recommendation

Immediately update Weaviate to version 1.38.0-rc.0 or later. Implement appropriate access controls and monitor logs for suspicious activity.

Other vulnerabilities in Weaviate

CVE-2026-59093High
In Weaviate before version 1.38.0, there is no verification that a principal assigning an RBAC role holds the permissions granted by that role. A user with the delegated assign_and_revoke_users or assign_and_revoke_groups permission can assign the built-in admin role to themselves or others, leading to privilege escalation to full database control.

Original NVD description (English source)

A vulnerability was identified in Weaviate up to 1.37.7. This vulnerability affects the function validateConfig of the file usecases/auth/authentication/apikey/client.go of the component Static API Key Handler. The manipulation of the argument StaticApiKey leads to authorization bypass. It is possible to initiate the attack remotely. The complexity of an attack is rather high. It is stated that the exploitability is difficult. The exploit is publicly available and might be used. Upgrading to version 1.38.0-rc.0 is able to resolve this issue. The identifier of the patch is 40f2cc32279f0f8a51016c3c6870a2c0c808e6c0. You should upgrade the affected component.