How severe is CVE-2017-8418?

CVE-2017-8418 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2017-8418 being actively exploited?

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

What products are affected by CVE-2017-8418?

CVE-2017-8418 affects Rubocop Project Rubocop. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-8418?

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

When was CVE-2017-8418 published?

CVE-2017-8418 was published on 2017-05-02 and last updated on 2026-06-17.

CVE-2017-8418

CVE-2017-8418 is a low-severity vulnerability in Rubocop Project Rubocop with a CVSS 3.x base score of 3.3. 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-668.

Key facts

Severity: Low (CVSS 3.x base score 3.3)
CVSS v2: 2.1
EPSS exploit prediction: 0% (33rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-668
Affected product: Rubocop Project Rubocop
Published: 2017-05-02
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2017-8418?: 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 severe is CVE-2017-8418?: CVE-2017-8418 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2017-8418 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-8418?: CVE-2017-8418 affects Rubocop Project Rubocop. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-8418?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-8418 published?: CVE-2017-8418 was published on 2017-05-02 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:rubocop_project:rubocop:*:*:*:*:*:*:*:*

Other CWE-668 (Exposure of Resource to Wrong Sphere) vulnerabilities

CVE-2025-2857 — Critical (CVSS 10.0): Following the recent Chrome sandbox escape (CVE-2025-2783), various Firefox developers identified a similar pattern in…
CVE-2019-8779 — Critical (CVSS 10.0): A logic issue applied the incorrect restrictions. This issue was addressed by updating the logic to apply the correct…
CVE-2012-1846 — Critical (CVSS 10.0): Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the sandbox protection mechanism by leveraging…
CVE-2022-43684 — Critical (CVSS 9.9): ServiceNow has released patches and an upgrade that address an Access Control List (ACL) bypass issue in ServiceNow…
CVE-2022-24900 — Critical (CVSS 9.9): Piano LED Visualizer is software that allows LED lights to light up as a person plays a piano connected to a computer.…
CVE-2019-16541 — Critical (CVSS 9.9): Jenkins JIRA Plugin 3.0.10 and earlier does not declare the correct (folder) scope for per-folder Jira site…

Browse all CWE-668 (Exposure of Resource to Wrong Sphere) vulnerabilities →