CVE-2018-3785: A command injection in git-dummy-commit v1.3.0 allows os level commands to be executed due to an unescaped par

Q: How do I fix CVE-2018-3785?

git-dummy-commit: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2018-3785 being exploited?

CVE-2018-3785 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-3785 affect?

CVE-2018-3785 affects git-dummy-commit. Severity is critical (CVSS 9.8). A command injection in git-dummy-commit v1.3.0 allows os level commands to be executed due to an unescaped parameter.

Q: How urgent is CVE-2018-3785?

Priority 67/100. Critical severity; EPSS top 9%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2018-3785 is a critical-severity flaw (CVSS 9.8) affecting git-dummy-commit. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A command injection in git-dummy-commit v1.3.0 allows os level commands to be executed due to an unescaped parameter.

Why this priority

Critical severity
EPSS top 9%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	4.0% (top 9%)
CISA exploited list	No
Weakness	CWE-78
Published	2018-08-17
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: git-dummy-commit project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-08-17 13:29 UTCPublished CVE record published
2026-06-17 01:57 UTCUpdated Record last modified

git-dummy-commit project git-dummy-commit DOWNGRADE

Affected: 1.3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.3.0

1. Check installed version

npm ls git-dummy-commit

2. No fixed release: DOWNGRADE to a release before 1.3.0

npm view git-dummy-commit versions npm install git-dummy-commit@"<1.3.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-3785?

git-dummy-commit: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-3785 being exploited?

CVE-2018-3785 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-3785 affect?

CVE-2018-3785 affects git-dummy-commit. Severity is critical (CVSS 9.8). A command injection in git-dummy-commit v1.3.0 allows os level commands to be executed due to an unescaped parameter.

How urgent is CVE-2018-3785?

Priority 67/100. Critical severity; EPSS top 9%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Git vulnerabilities

References

← Back to latest CVEs