Read the docs
TI-2017-05973 Aliases CVE-2017-8418GHSA-wmjf-jpjj-9f3j

RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit…

Priority LOW 16CWE-668Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.0 · NVD. Fix status from CNA and GitHub.

Summary

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 it matters now

EPSS 0.00409 35th percentileScored 2026-11-07
Public exploit Yes 2 exploit referencesTagged by NVD
Fix Fixed rubocop (RubyGems): 0.49.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
—rubocop (RubyGems)before 0.49.00.49.0Patch availableGHSA-wmjf-jpjj-9f3j
  • — Vendor— Affected all versions Fixed in — No fix listed CNA
  • rubocop (RubyGems) Vendor— Affected before 0.49.0 Fixed in 0.49.0 Patch available GHSA-wmjf-jpjj-9f3j

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:rubocop_project:rubocop:*:*:*:*:*:*:*:*up to 0.48.1VulnerableRubocop Project
  • cpe:2.3:a:rubocop_project:rubocop:*:*:*:*:*:*:*:* Versions up to 0.48.1 Vulnerable ·Rubocop Project

Remediation

  • Fix · GHSA-wmjf-jpjj-9f3j rubocop (RubyGems) Fixed in 0.49.0 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2017-8418
  2. 2026-10-03 Alias added: GHSA-wmjf-jpjj-9f3j

References

Sources