PatchTheCVECVE-2017-8418: RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with
CVE-2017-8418 is a low-severity flaw (CVSS 3.3) affecting rubocop. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with cache files belonging to other users.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 3.3 (Low) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.4% (top 65%) |
| CISA exploited list | No |
| Weakness | CWE-668 |
| Published | 2017-05-02 |
| 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-2017-8418?
rubocop: upgrade to newer than 0.48.1. Exact commands for each OS are on this page.
Is CVE-2017-8418 being exploited?
CVE-2017-8418 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-8418 affect?
CVE-2017-8418 affects rubocop. Severity is low (CVSS 3.3). RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with cache files belonging to other users.
How urgent is CVE-2017-8418?
Priority 25/100. Public exploit reference