GHSA-jcgr-9698-82jx
GHSA-jcgr-9698-82jx is a security vulnerability in @floffah/build. O3 Security confirms whether GHSA-jcgr-9698-82jx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Neutralization of Special Elements used in a Command ('Command Injection') in @floffah/build
Real-World Exposure
@floffah/buildReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Impact
If you are using the esbuild target or command you are at risk of code/option injection. Attackers can use the command line option to maliciously change your settings in order to damage your project.
Patches
The problem has been patched in v1.0.0 as it uses a proper method to pass configs to esbuild/estrella.
Workarounds
There is no work around. You should update asap.
Notes
This notice is mainly just to make sure people update to the latest version. This isn't that bad, but should encourage you to update.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @floffah/build | all versions | 1.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @floffah/build. 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.
Fix
Update @floffah/build to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jcgr-9698-82jx 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.
How O3 protects you
O3 pinpoints whether GHSA-jcgr-9698-82jx 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-jcgr-9698-82jx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jcgr-9698-82jx in your dependencies?
O3 detects GHSA-jcgr-9698-82jx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.