GHSA-rj44-gpjc-29r7 is a medium-severity (CVSS 6.4) OS Command Injection vulnerability in @thi.ng/egf. O3 Security confirms whether GHSA-rj44-gpjc-29r7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
[thi.ng/egf] Potential arbitrary code execution of `#gpg`-tagged property values
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@thi.ng/egfnpmDescription
Impact
Potential for arbitrary code execution in #gpg-tagged property values (only if decrypt: true option is enabled)
Patches
A fix has already been released as v0.4.0
Workarounds
By default, EGF parse functions do NOT attempt to decrypt values (since GPG is only available in non-browser env).
However, if GPG encrypted values are used/required:
- Perform a regex search for
#gpg-tagged values in the EGF source file/string and check for backtick (`) chars in the encrypted value string - Replace/remove them or skip parsing if present...
References
https://github.com/thi-ng/umbrella/security/advisories/GHSA-rj44-gpjc-29r7#advisory-comment-65261
For more information
If you have any questions or comments about this advisory, please open an issue in the thi.ng/umbrella repo, of which this package is part of.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @thi.ng/egf | all versions | 0.4.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @thi.ng/egf. 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 @thi.ng/egf to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rj44-gpjc-29r7 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-rj44-gpjc-29r7 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-rj44-gpjc-29r7. 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-rj44-gpjc-29r7 in your dependencies?
O3 detects GHSA-rj44-gpjc-29r7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.