Command Injection in priest-runner
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Code execution
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-77.
Summary
All versions of `priest-runner` are vulnerable to Command Injection. The package fails to sanitize input and passes it directly to a `spawn` call, which may allow attackers to execute arbitrary code in the system. The `PriestController.prototype.createChild ` function is vulnerable since the `spawn` parameters come from a POST request body. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | priest-runner (npm) | 0.0.0 and later | — | No fix listed | GHSA-9px9-f7jw-fwhj |
- priest-runner (npm) Vendor— Affected 0.0.0 and later Fixed in — No fix listed GHSA-9px9-f7jw-fwhj
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-9px9-f7jw-fwhj
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences