Bloom Uncontrolled Search Path Element vulnerabilityGHSA-fgwp-pwqq-g3w4
HIGHFix: bits-and-blooms/bloom@658f139GHSA-fgwp-pwqq-g3w4 is a high-severity (CVSS 7.8) CWE-427 vulnerability in github.com/bits-and-blooms/bloom. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/bits-and-blooms/bloom — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-fgwp-pwqq-g3w4.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/bits-and-blooms/bloomReal-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
Uncontrolled Search Path Element in GitHub repository bits-and-blooms/bloom prior to 3.3.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/bits-and-blooms/bloom | all versions | 3.3.1go get github.com/bits-and-blooms/bloom@v3.3.1 |
Affected Products
bloombloom_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bits-and-blooms/bloom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/bits-and-blooms/bloom to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fgwp-pwqq-g3w4 is resolved across your whole dependency graph.
Workarounds
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.
Frequently Asked Questions
Is GHSA-fgwp-pwqq-g3w4 in your dependencies?
Find it across Go, including transitive dependencies.