LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19486: Git before 2.19.2 on Linux and UNIX executes commands from the current working directory (as if '.' were at...

Git before 2.19.2 on Linux and UNIX executes commands from the current working directory (as if '.' were at the end of $PATH) in certain cases involving the run_command() API and run-command.c, because there was a dangerous change from execvp to execv during 2017.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older Git versions on Linux and UNIX could accidentally run a program from the current folder when performing certain internal command launches. If an attacker can place a malicious executable where a user or automation runs Git, Git may run the wrong program. The source bundle does not show active exploitation or CVSS scoring.

Executive priority

Treat this as a targeted hygiene issue for engineering infrastructure, not an internet-wide emergency. Prioritize old Git installations in build and release paths because unintended command execution there can affect source integrity and deployment trust.

Technical view

Git before 2.19.2 used vulnerable run_command() behavior in run-command.c after a 2017 change from execvp to execv. In certain cases, command lookup behaved as if the current directory were appended to PATH, allowing unintended execution from the working directory on Linux and UNIX systems.

Likely exposure

Exposure is most likely on developer workstations, CI runners, build servers, and UNIX-like container images running Git before 2.19.2. Risk depends on whether users or automation run Git from directories writable or influenced by another party.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Practical abuse appears to require a vulnerable Git version, a crafted executable in the current working directory, and a Git workflow that triggers the affected command-launch path.

Researcher notes

Evidence is limited to the CVE description, Git commit and release notes, and vendor advisories. No CVSS, CWE, affected CPEs, or exploitation reports are included in the bundle, so severity and exposure should be validated against local Git usage patterns.

Mitigation direction

  • Upgrade Git to 2.19.2 or later where vendor packages allow.
  • Apply distribution fixes from Red Hat, Ubuntu, Gentoo, or relevant vendor advisories.
  • Prioritize CI, build, release, and developer systems using old Git packages.
  • Check vendor guidance if fixed package availability is unclear.

Validation and detection

  • Inventory Git versions on Linux and UNIX systems.
  • Check CI runner and container images for Git before 2.19.2.
  • Confirm vendor security updates are installed on managed hosts.
  • Review build workspaces for untrusted write access before Git execution.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-19486 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.