CVE-2017-11353: yadm (yet another dotfile manager) 1.10.0 has a race condition (related to the behavior of git commands in set

This month

MEDIUM 5.9REMOTEDOWNGRADE

CVE-2017-11353 is a medium-severity flaw (CVSS 5.9) affecting yadm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Remotely exploitable, no login, no user action

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

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.8% (top 44%)
CISA exploited list	No
Weakness	CWE-362
Published	2017-07-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: yadm project

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

Am I affected?

Timeline

2017-07-17 13:18 UTCPublished CVE record published
2026-06-17 01:01 UTCUpdated Record last modified

yadm project yadm DOWNGRADE

Affected: 1.10.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.10.0

1. Check installed version

apt-cache policy yadm || rpm -q yadm || yadm --version

2. No fixed release: DOWNGRADE to a release before 1.10.0 (Debian / Ubuntu)

apt-cache madison yadm sudo apt install yadm=<VERSION_BEFORE_1.10.0> sudo apt-mark hold yadm

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list yadm sudo dnf downgrade yadm-<VERSION_BEFORE_1.10.0> sudo dnf versionlock add yadm

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-2017-11353?

yadm: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-11353 being exploited?

CVE-2017-11353 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-2017-11353 affect?

CVE-2017-11353 affects yadm. Severity is medium (CVSS 5.9). 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 urgent is CVE-2017-11353?

Priority 40/100. Remotely exploitable, no login, no user action

Software pages

Git vulnerabilities

References

← Back to latest CVEs