CVE-2019-1348

What it is

An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2020-01-24 22:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:28 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 3.3 LOW (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2020-01-24 22:15 UTC

Last modified

2026-06-17 02:28 UTC

Exploit probability

0.4% · EPSS, next 30 days

Record status

Modified

Affected

• git-scm Git < 2.14.6
• git-scm Git < 2.15.4
• git-scm Git < 2.16.6
• git-scm Git < 2.17.3
• git-scm Git < 2.18.2
• git-scm Git < 2.19.3
• git-scm Git < 2.20.2
• git-scm Git < 2.21.1

Attack profile CVSS 3.1 · 3.3

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-1348.md and follow it. Check whether this project is affected by CVE-2019-1348. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge