Unratedamended

Command Injection in dot

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

npm dot
Affected
<= 1.1.2
Fixed in
no fixed version recorded

Sources

Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-4859-gpc7-4j66 lists affected ranges: npm dot >=0 <=1.1.2
VerifiedObserved 24 Oct 2026, 04:13 UTCStructured OSV record; GitHub-reviewed advisory.
GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4859-gpc7-4j66 lists affected ranges: npm dot >=0 <=1.1.2
VerifiedObserved 26 Oct 2026, 12:06 UTCStructured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation

Exploitation: No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS: not scored
EPSS: No dated EPSS signal available.

Source description

As published by the source; long descriptions are shortened.

All versions of dot are vulnerable to Command Injection. The template compilation may execute arbitrary commands if an attacker can inject code in the template or if a Prototype Pollution-like vulnerability can be exploited to alter an Object's prototype.

Dates and revisions

Published by the source: 5 Jun 2019, 21:24 UTC
Last modified by the source: 9 Jan 2023, 05:01 UTC
Source last checked: 26 Oct 2026, 12:06 UTC

Revision 2 · amended · 26 Oct 2026
Amended from ghsa record GHSA-4859-gpc7-4j66
Revision 1 · created · 24 Oct 2026
Published from osv record GHSA-4859-gpc7-4j66

Agent brief

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

# Patch Next advisory brief: GHSA-4859-gpc7-4j66

Advisory: Command Injection in dot
IDs: GHSA-4859-gpc7-4j66
Record: https://patchnext.com/advisories/ghsa-4859-gpc7-4j66 (revision 2, source checked 26 Oct 2026, 12:06 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 response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm dot: affected <= 1.1.2

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dot.
- 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-4859-gpc7-4j66 (OSV record GHSA-4859-gpc7-4j66 lists affected ranges: npm dot >=0 <=1.1.2)
- Verified: https://github.com/advisories/GHSA-4859-gpc7-4j66 (GitHub-reviewed advisory GHSA-4859-gpc7-4j66 lists affected ranges: npm dot >=0 <=1.1.2)

Commands are suggestions: review each one before running it.

Loading voting…