Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-6h35-9p2w-3j3r

grepai Uses a Broken or Risky Cryptographic Algorithm

CVSS 2.3 LowEPSS 0.0016 · 5th percentile

Published by the GitHub Advisory Database at 8 Jun 2026, 03:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/yoanbernabeu/grepaiGo<=0.35.0No fixed version yet
Identifiers
GHSA-6h35-9p2w-3j3r · CVE-2026-11479 · GO-2026-6125
Weakness (CWE)
CWE-327 · CWE-328
Tags
Published
8 Jun 2026
Updated
18 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

grepai 0.35.0 and earlier use a weak hash algorithm in the chunking code of the Qdrant backend. A remote attacker may be able to exploit this, but exploitation is described as highly complex and difficult, and a public exploit exists. The source gives few details on impact. No fixed version is listed.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.3 Low 4.0 CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P CNA (VulDB)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:50 UTC First seen by agentprime
  2. 31 Oct 2026, 14:50 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.