yoanbernabeu grepai 0.35.0 Qdrant Backend indexer/chunker.go weak hash
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.78 |
Summary
A vulnerability has been found in yoanbernabeu grepai 0.35.0 and classified as problematic. Impacted is an unknown function of the file indexer/chunker.go of the component Qdrant Backend. Performing a manipulation results in weak hash. This vulnerability is cataloged as CVE-2026-11479. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. The pull request to fix this issue awaits acceptance.
Details
A vulnerability classified as problematic has been found in yoanbernabeu grepai 0.35.0. This affects an unknown part of the file indexer/chunker.go of the component Qdrant Backend. The manipulation with an unknown input leads to a weak hash vulnerability. CWE is classifying the issue as CWE-328. The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack). This is going to have an impact on integrity, and availability.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-11479. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Technical details and a public exploit are known. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The pull request to fix this issue awaits acceptance.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 3.8
VulDB Base Score: 4.2
VulDB Temp Score: 3.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Weak hashCWE: CWE-328 / CWE-327 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/07/2026 Advisory disclosed06/07/2026 VulDB entry created
06/07/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 247
Status: Not defined
Confirmation: 🔒
CVE: CVE-2026-11479 (🔒)
GCVE (CVE): GCVE-0-2026-11479
GCVE (VulDB): GCVE-100-369099
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/07/2026 11:50Changes: 06/07/2026 11:50 (58)
Complete: 🔍
Submitter: Dem000
Cache ID: 216::103
Submit
Accepted
- Submit #833971: yoanbernabeu grepai 0.35.0 Improper Isolation (by Dem000)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.