[thi.ng/egf] Potential arbitrary code execution of `#gpg`-tagged property valuesGHSA-rj44-gpjc-29r7
MEDIUMFix: thi-ng/umbrella@88f6165GHSA-rj44-gpjc-29r7 is a medium-severity (CVSS 6.4) OS Command Injection vulnerability in @thi.ng/egf. A fix is available for @thi.ng/egf — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-rj44-gpjc-29r7 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
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.0npm install @thi.ng/egf@0.4.0 |
Affected Products
\@thi.ng\/egf\@thi.ng\/egf_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @thi.ng/egf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-rj44-gpjc-29r7 in your dependencies?
Find it across npm, including transitive dependencies.