Command Injection in ascii-art

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Versions of ascii-art before 1.4.4 are vulnerable to command injection. This is exploitable when user input is passed into the argument of the ascii-art preview command. Example Proof of concept: ascii-art preview 'doom"; touch /tmp/malicious; echo "' Given that the input is passed on the command line and none of the api methods are vulnerable to this, the likely exploitation vector is when the ascii-art comment is being called programmatically using something like execFile. Recommendation Update to version 1.4.4 or later.

Published by the source

1 Sep 2020, 21:19 UTC

Last modified by the source

9 Jan 2023, 05:04 UTC

Source last checked

26 Oct 2026, 12:09 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9hqj-38j2-5jgm

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9hqj-38j2-5jgm

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

# Patch Next advisory brief: GHSA-9hqj-38j2-5jgm

Advisory: Command Injection in ascii-art
IDs: GHSA-9hqj-38j2-5jgm
Record: https://patchnext.com/advisories/ghsa-9hqj-38j2-5jgm (revision 2, source checked 26 Oct 2026, 12:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ascii-art 1.4.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm ascii-art: affected <= 1.4.2; fixed in 1.4.4

## Suggested inspection (read-only)
- `npm ls ascii-art --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 ascii-art.
- 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://osv.dev/vulnerability/GHSA-9hqj-38j2-5jgm (OSV record GHSA-9hqj-38j2-5jgm lists affected ranges: npm ascii-art >=0 <1.4.4 (fixed))
- Verified: https://github.com/advisories/GHSA-9hqj-38j2-5jgm (GitHub-reviewed advisory GHSA-9hqj-38j2-5jgm lists affected ranges: npm ascii-art >=0 <=1.4.2)

Commands are suggestions: review each one before running it.