CVE-2025-48069 is a medium-severity (CVSS 6.6) OS Command Injection vulnerability in github.com/Shopify/ejson2env/v2. A fix is available for github.com/Shopify/ejson2env/v2 — see the affected versions and patch details below.
ejson2env has insufficient input sanitization
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-48069.
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/Shopify/ejson2env/v2🐹github.com/Shopify/ejson2env💎ejson2envReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go, RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The ejson2env tool has a vulnerability related to how it writes to stdout. Specifically, the tool is intended to write an export statement for environment variables and their values. However, due to inadequate output sanitization, there is a potential risk where variable names or values may include malicious content, resulting in additional unintended commands being output to stdout. If this output is improperly utilized in further command execution, it could lead to command injection vulnerabilities, allowing an attacker to execute arbitrary commands on the host system.
Details
The vulnerability exists because environment variables are not properly sanitized during the decryption phase, which enables malicious keys or encrypted values to inject commands.
Impact
An attacker with control over .ejson files can inject commands in the environment where source $(ejson2env) or eval ejson2env are executed.
Mitigation
- Update to a version of
ejson2envthat sanitizes the output during decryption or - Do not use
ejson2envto decrypt untrusted user secrets or - Do not evaluate or execute the direct output from
ejson2envwithout removing nonprintable characters.
Credit
Thanks to security researcher Demonia for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/Shopify/ejson2env/v2 | all versions | 2.0.8go get github.com/Shopify/ejson2env/v2@v2.0.8 |
| 🐹Go | github.com/Shopify/ejson2env | all versions | No fix |
| 💎RubyGems | ejson2env | all versions | 2.0.8bundle update ejson2env --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Shopify/ejson2env/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/Shopify/ejson2env/v2 to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48069 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 CVE-2025-48069 in your dependencies?
Find it across Go, RubyGems, including transitive dependencies.