Insufficient input sanitization in ejson2env

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.6 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2025-48069: 1.42% estimated exploitation activity in the next 30 days; percentile 72.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 ejson2env that sanitizes the output…

Published by the source

21 May 2025, 18:32 UTC

Last modified by the source

27 May 2025, 19:00 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2c47-m757-32g6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-48069

Advisory: Insufficient input sanitization in ejson2env
IDs: CVE-2025-48069, GHSA-2c47-m757-32g6
Record: https://patchnext.com/advisories/cve-2025-48069 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ejson2env 2.0.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems ejson2env: affected < 2.0.8; fixed in 2.0.8

## Suggested inspection (read-only)
- RubyGems ejson2env: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ejson2env.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2c47-m757-32g6 (GitHub-reviewed advisory GHSA-2c47-m757-32g6 lists affected ranges: RubyGems ejson2env >=0 <2.0.8)

Commands are suggestions: review each one before running it.