CVE-2026-11500 json
Weaviate Static API Key client.go validateConfig authorization
published 5mo ago modified 2mo ago also GHSA-jqpm-wf57-qx5c , GO-2026-6140 , EUVD-2026-35034
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/weaviate/weaviate 1.38.0-rc.0
- n/a Weaviate 1.38.0-rc.0
- govulncheck-vulndb SLES for SAP applications 16.0, SLES 16.0 0.0.20260827T195228-160000.1.1
suse advisories SUSE-SU-2026:23625-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260827T195228-160000.1.1
opensuse advisories openSUSE-SU-2026:21761-1
Is CVE-2026-11500 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/weaviate/weaviate/issues/11392 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.3 | 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 |
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C |
| CNA | 3.0 | 5.0 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C |
| CNA | 2.0 | 4.6 | AV:N/AC:H/Au:S/C:P/I:P/A:P/E:POC/RL:OF/RC:C |
| CNA | 4.0 | 1.3 | 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 |
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 2.0 | 4.6 | AV:N/AC:H/Au:S/C:P/I:P/A:P |
| GitHub | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/weaviate/weaviate | <1.38.0-rc.0 |
1.38.0-rc.0 |
Affected products
- n/a Weaviate
Classification
References
-
github.com
/weaviate/weaviate/commit/40f2cc32279f0f8a51016c3c6870a2c0c808e6c0
patch, web
-
github.com
/weaviate/weaviate/releases/tag/v1.38.0-rc.0
patch, web
-
github.com
/weaviate/weaviate/issues/11392
exploit, issue-tracking, web, report
-
vuldb.com
/vuln/369120
vdb-entry, technical-description, web
-
vuldb.com
/vuln/369120/cti
signature, permissions-required, web
-
vuldb.com
/cve/CVE-2026-11500
third-party-advisory, web
-
vuldb.com
/submit/835080
third-party-advisory, web
-
github.com
/weaviate/weaviate/
product
-
nvd.nist.gov
/vuln/detail/CVE-2026-11500
advisory
-
github.com
/weaviate/weaviate
package
-
github.com
/advisories/GHSA-jqpm-wf57-qx5c
advisory
Sources
- CVE List CVE-2026-11500
- GitHub Advisory GHSA-jqpm-wf57-qx5c
- NVD CVE-2026-11500
- OSV GO-2026-6140
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.