### Impact
This vulnerability is a type conversion issue that affects users of Weaviate Server versions 1.20.0 and earlier.
Who is impacted: Users of Weaviate Server versions 1.20.0 and earlier are impacted by this vulnerability.
### Patches
A patch has been developed for this vulnerability.
Patch releases 1.20.6, 1.19.13, and 1.18.6 are fixing this vulnerability in each respective minor version release.
Users are strongly recommended to upgrade to one of these patched versions to address the vulnerability.
Keeping software up-to-date is crucial to avoid security vulnerabilities.
### Workarounds
There are no known workarounds to fix or remediate this vulnerability without upgrading.
Users must upgrade to a patched version to mitigate the risk.
### References
* https://github.com/weaviate/weaviate/releases/tag/v1.18.6
* https://github.com/weaviate/weaviate/releases/tag/v1.19.13
* https://github.com/weaviate/weaviate/releases/tag/v1.20.6
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Aug 21, 2023, 12:00:00 AM
dateUpdated: Oct 7, 2024, 5:03:00 PM
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-617
Original publisher date fields
published: 2023-08-21T17:15:48.127
lastModified: 2026-06-17T06:11:25.937
1 source CPE criteria · context only
cpe:2.3:a:weaviate:weaviate:1.20.0:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.