Is there a public PoC exploit available for CVE-2026-11500?

Yes, a public proof-of-concept exploit is available for CVE-2026-11500. Prioritise patching immediately. EPSS: 0.1%.

Is there a patch available for CVE-2026-11500?

Yes, a patch is available for CVE-2026-11500. Update the affected software to the latest version immediately.

Weaviate CVE-2026-11500

Q: What is the CVSS score of CVE-2026-11500?

CVE-2026-11500 has a CVSS 4.0 base score of 1.3 (Low). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

EUVD-2026-35034 LOW

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-06-08 VulDB

GHSA-jqpm-wf57-qx5c

Authentication Bypass N A Weaviate

1.3

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

1.3 LOW

CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jun 08, 2026 - 13:42 vuln.today

Analysis Generated

Jun 08, 2026 - 13:42 vuln.today

Severity Changed

Jun 08, 2026 - 10:22 NVD

MEDIUM LOW

CVSS changed

Jun 08, 2026 - 10:22 NVD

5.0 (MEDIUM) 1.3 (LOW)

DescriptionCVE.org

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.

AnalysisAI

Authorization bypass in Weaviate's Static API Key Handler (versions 1.37.0-1.37.7) stems from the validateConfig function failing to reject duplicate API keys mapped to distinct users, allowing key-to-user resolution to resolve ambiguously. An authenticated low-privilege attacker holding a duplicated key can authenticate to Weaviate and be resolved as an unintended user identity, bypassing user-level authorization controls. Publicly available exploit code exists (GitHub issue #11392), though the CVSS 4.0 score of 1.3 reflects high attack complexity and the authenticated, misconfiguration-dependent nature of the attack - no public exploitation or CISA KEV listing has been identified at time of analysis.

Technical ContextAI

Weaviate is an open-source vector database that supports Static API Key authentication via a configuration-driven handler in usecases/auth/authentication/apikey/client.go. The StaticApiKey component maps parallel arrays - AllowedKeys and Users - to associate API key values with user identities. The root cause (CWE-639: Authorization Bypass Through User-Controlled Key) arises because validateConfig did not enforce uniqueness across AllowedKeys: the same key value could be assigned to two different user entries (e.g., AllowedKeys: ['secret-key', 'secret-key'], Users: ['jane', 'jessica']). The commit diff at 40f2cc32279f0f8a51016c3c6870a2c0c808e6c0 shows the fix adds a seenKeys map to detect and reject duplicate entries with the error 'keys must be unique'. When duplicates exist, key lookup can resolve to an unintended user identity, effectively bypassing the intended per-user authorization boundary. CPE: cpe:2.3:a:n/a:weaviate:*:*:*:*:*:*:*:*.

RemediationAI

Upgrade Weaviate to version 1.38.0-rc.0 or later, which incorporates the fix at commit 40f2cc32279f0f8a51016c3c6870a2c0c808e6c0 (https://github.com/weaviate/weaviate/commit/40f2cc32279f0f8a51016c3c6870a2c0c808e6c0). Note that v1.38.0-rc.0 is a release candidate; organizations with strict stability requirements should monitor for a stable v1.38.x GA release before deploying in production and evaluate release candidate risk accordingly. As an immediate compensating control prior to patching, audit the Static API Key configuration and ensure no duplicate values exist in the AllowedKeys array - each user must have a unique key value. Removing duplicate keys eliminates the exploitable condition entirely, as the fix enforces exactly this invariant. If the Static API Key feature is not actively in use, disabling it removes all exposure from this vulnerability without impacting OIDC or other authentication mechanisms Weaviate supports.