How severe is CVE-2017-11353?

CVE-2017-11353 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2017-11353 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-11353?

CVE-2017-11353 affects Yadm Project Yadm. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-11353?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2017-11353 published?

CVE-2017-11353 was published on 2017-07-17 and last updated on 2026-06-17.

CVE-2017-11353

CVE-2017-11353 is a medium-severity vulnerability in Yadm Project Yadm with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.

Key facts

Severity: Medium (CVSS 3.x base score 5.9)
CVSS v2: 4.3
EPSS exploit prediction: 1% (51st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-362
Affected product: Yadm Project Yadm
Published: 2017-07-17
Last modified: 2026-06-17

Description

yadm (yet another dotfile manager) 1.10.0 has a race condition (related to the behavior of git commands in setting permissions for new files and directories), which potentially allows access to SSH and PGP keys.

Frequently asked questions

What is CVE-2017-11353?: yadm (yet another dotfile manager) 1.10.0 has a race condition (related to the behavior of git commands in setting permissions for new files and directories), which potentially allows access to SSH and PGP keys.
How severe is CVE-2017-11353?: CVE-2017-11353 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2017-11353 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-11353?: CVE-2017-11353 affects Yadm Project Yadm. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-11353?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-11353 published?: CVE-2017-11353 was published on 2017-07-17 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:yadm_project:yadm:1.10.0:*:*:*:*:*:*:*

Other CWE-362 (Race Condition) vulnerabilities

CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…

Browse all CWE-362 (Race Condition) vulnerabilities →