Advisory record · GHSA-q76h-p6jh-9rw3

grepai Uses a Broken or Risky Cryptographic Algorithm

CVSS 2.0 LowEPSS 0.0008 · 1st 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-q76h-p6jh-9rw3 · CVE-2026-11481 · GO-2026-6128
Weakness (CWE)
CWE-327 · CWE-328
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.

The grepai Go module github.com/yoanbernabeu/grepai, versions up to and including 0.35.0, has a weak hash issue in the PostgresStore.LookupByContentHash function, which is used by its Postgres embedding cache. An attacker with local access could exploit this with considerable effort, and the source says exploitation is difficult and a public exploit exists. 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.0 Low 4.0 CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P CNA (VulDB)
  • CISA KEV Not listed.
  • EPSS 0.0008, the 1st percentile, on 11 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.