PatchTheCVECVE-2019-15716: WTF before 0.19.0 does not set the permissions of config.yml, which might make it easier for local attackers t
CVE-2019-15716 is a medium-severity flaw (CVSS 5.5) affecting wtf. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
WTF before 0.19.0 does not set the permissions of config.yml, which might make it easier for local attackers to read passwords or API keys if the permissions were misconfigured or were based on unsafe OS defaults.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.5 (Medium) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.5% (top 60%) |
| CISA exploited list | No |
| Weakness | CWE-276 |
| Published | 2019-08-28 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-2019-15716?
wtf: upgrade to 0.19.0. Exact commands for each OS are on this page.
Is CVE-2019-15716 being exploited?
CVE-2019-15716 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-2019-15716 affect?
CVE-2019-15716 affects wtf. Severity is medium (CVSS 5.5). WTF before 0.19.0 does not set the permissions of config.yml, which might make it easier for local attackers to read passwords or API keys if the permissions were misconfigured or were based on unsafe OS defaults.
How urgent is CVE-2019-15716?
Priority 34/100. Public exploit reference