CVE-2026-11500

MEDIUMPre-NVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

Score 5.0 from GitHub Security Advisory (severity: LOW) published 2026-06-08. A secondary CVSS source baseline 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
5.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.0
EG Score
5.0MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity50% × 45%
The EG Score, 5.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 8, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jun 17, 2026
Patch available. Sources: github_commit, github_release.
github_release Patch Available

v1.38.0-rc.0 - HFresh, Namespaces, Nested Object Filtering, Alter Schema Reindex property

Patch available: weaviate/weaviate v1.38.0-rc.0 (pre-release)

https://github.com/weaviate/weaviate/releases/tag/v1.38.0-rc.0
generic

Duplicate static API keys can authenticate as the wrong user · Issue #11392 · weaviate/weaviate · GitHub

https://github.com/weaviate/weaviate/issues/11392
github_commit

commit 40f2cc32279f (weaviate/weaviate)

Fix landed in weaviate/weaviate commit 40f2cc32279f — awaiting tagged release

https://github.com/weaviate/weaviate/commit/40f2cc32279f0f8a51016c3c6870a2c0c808e6c0
generic

GitHub - weaviate/weaviate: Weaviate is an open-source vector database that stores both objects and vectors, allowing for the combination of vector search with structured filtering with the fault tolerance and scalability of a cloud-native database​. · GitHub

https://github.com/weaviate/weaviate/

Vendor Advisories for CVE-2026-11500(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/weaviate/weaviate—
  • every version up to 1.38.0-rc.0: fixed in 1.38.0-rc.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 180 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 18:25 UTCEG score recompute
  2. 2026-10-11 14:59 UTCEG score recompute
  3. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-03 10:39 UTCOSV refresh
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  21. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-09-14 04:57 UTCEG score recompute
  23. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  24. 2026-09-12 20:36 UTCOSV refresh
  25. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 74 more
  1. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  3. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  4. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  7. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  11. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  12. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  13. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-08-25 01:35 UTCEG score recompute
  17. 2026-08-23 11:58 UTCEG score recompute
  18. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-08-21 12:43 UTCEG score recompute
  21. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-08-20 09:34 UTCEG score recompute
  23. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-08-16 15:57 UTCEG score recompute
  26. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  27. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  28. 2026-08-15 13:58 UTCEG score recompute
  29. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  30. 2026-08-14 12:00 UTCEG score recompute
  31. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  32. 2026-08-13 10:04 UTCEG score recompute
  33. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  34. 2026-08-12 08:08 UTCEG score recompute
  35. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  36. 2026-08-11 05:53 UTCEG score recompute
  37. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  38. 2026-08-10 03:58 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  40. 2026-08-09 02:03 UTCEG score recompute
  41. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  42. 2026-08-08 00:08 UTCEG score recompute
  43. 2026-08-06 22:12 UTCEG score recompute
  44. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  45. 2026-08-05 20:17 UTCEG score recompute
  46. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  47. 2026-08-04 17:18 UTCEG score recompute
  48. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  49. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  50. 2026-08-03 15:22 UTCEG score recompute
  51. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  52. 2026-08-02 12:54 UTCEG score recompute
  53. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  54. 2026-08-01 10:58 UTCEG score recompute
  55. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  56. 2026-07-31 04:57 UTCEG score recompute
  57. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  58. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  59. 2026-07-29 06:36 UTCEG score recompute
  60. 2026-07-29 06:36 UTCGHSA enrichmentGHSA-jqpm-wf57-qx5c · GitHub severity LOW · GitHub CVSS 5.0
  61. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  62. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  63. 2026-07-27 09:13 UTCEG score recompute
  64. 2026-07-27 09:13 UTCGHSA enrichmentGHSA-jqpm-wf57-qx5c · GitHub severity LOW · GitHub CVSS 5.0
  65. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  66. 2026-07-26 07:16 UTCEG score recompute
  67. 2026-07-26 07:16 UTCGHSA enrichmentGHSA-jqpm-wf57-qx5c · GitHub severity LOW · GitHub CVSS 5.0
  68. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  69. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  70. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  71. 2026-07-23 03:04 UTCEG score recompute
  72. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  73. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  74. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile

Frequently asked(5)

What is CVE-2026-11500?
CVE-2026-11500 is a medium-severity vulnerability; its CVE record was published on June 8, 2026. 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…
When was the CVE record for CVE-2026-11500 published?
The CVE record for CVE-2026-11500 was published on June 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-11500 actively exploited?
CVE-2026-11500 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11500?
CVE-2026-11500 has a CVSS base score of 5.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11500?
A fix for CVE-2026-11500 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-11500 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11500

Explore →

Is Your Infrastructure Affected by CVE-2026-11500?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.