Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-6h35-9p2w-3j3r

MEDIUM

GHSA-6h35-9p2w-3j3r is a medium-severity (CVSS 4.2) Broken Cryptographic Algorithm vulnerability in github.com/yoanbernabeu/grepai. O3 Security confirms whether GHSA-6h35-9p2w-3j3r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

grepai Uses a Broken or Risky Cryptographic Algorithm

Also known asCVE-2026-11479
Published
Jun 8, 2026
Updated
Jul 28, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Blast Radius

1 pkg affected
🐹github.com/yoanbernabeu/grepai

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability has been found in yoanbernabeu grepai 0.35.0. This issue affects some unknown processing of the file indexer/chunker.go of the component Qdrant Backend. Such manipulation leads to use of weak hash. The attack may be performed from remote. Attacks of this nature are highly complex. The exploitability is assessed as difficult. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/yoanbernabeu/grepaiall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/yoanbernabeu/grepai. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of github.com/yoanbernabeu/grepai has shipped for GHSA-6h35-9p2w-3j3r yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-6h35-9p2w-3j3r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6h35-9p2w-3j3r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability has been found in yoanbernabeu grepai 0.35.0. This issue affects some unknown processing of the file indexer/chunker.go of the component Qdrant Backend. Such manipulation leads to use of weak hash. The attack may be performed from remote. Attacks of this nature are highly complex. The exploitability is assessed as difficult. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
O3 Security · Impact-Aware SCA

Is GHSA-6h35-9p2w-3j3r in your dependencies?

O3 detects GHSA-6h35-9p2w-3j3r across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.