How severe is GHSA-4859-gpc7-4j66?

No CVSS score has been assigned to GHSA-4859-gpc7-4j66 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4859-gpc7-4j66?

GHSA-4859-gpc7-4j66 affects the following packages: dot (npm). Ecosystems affected: npm.

How do I fix GHSA-4859-gpc7-4j66?

The records we use list no patched version of dot for GHSA-4859-gpc7-4j66. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-4859-gpc7-4j66 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dot, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4859-gpc7-4j66 if there is no patch (or I can't update yet)?

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.

Is GHSA-4859-gpc7-4j66 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4859-gpc7-4j66 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-4859-gpc7-4j66 published, and has it been updated?

GHSA-4859-gpc7-4j66 was published on June 5, 2019 and was last updated on August 4, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Command Injection in dotGHSA-4859-gpc7-4j66

GHSA-4859-gpc7-4j66 is a remote code execution vulnerability in dot. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Jun 5, 2019

Updated

Aug 4, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 4, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

569other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

dotnpm

433Kdownloads / week

Description

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`dot`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dot, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of dot for GHSA-4859-gpc7-4j66. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

O3 Security · Impact-Aware SCA

Is GHSA-4859-gpc7-4j66 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works