CVE-2017-7540
CVE-2017-7540 is a critical-severity vulnerability in Safemode Project Safemode with a CVSS 3.x base score of 9.8. 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-184.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- CVSS v2: 7.5
- EPSS exploit prediction: 2% (73rd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-184
- Affected product: Safemode Project Safemode
- Published:
- Last modified:
Description
rubygem-safemode, as used in Foreman, versions 1.3.2 and earlier are vulnerable to bypassing safe mode limitations via special Ruby syntax. This can lead to deletion of objects for which the user does not have delete permissions or possibly to privilege escalation.
Frequently asked questions
- What is CVE-2017-7540?
- rubygem-safemode, as used in Foreman, versions 1.3.2 and earlier are vulnerable to bypassing safe mode limitations via special Ruby syntax. This can lead to deletion of objects for which the user does not have delete permissions or possibly to privilege escalation.
- How severe is CVE-2017-7540?
- CVE-2017-7540 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2017-7540 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2017-7540?
- CVE-2017-7540 affects Safemode Project Safemode. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2017-7540?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2017-7540 published?
- CVE-2017-7540 was published on 2017-07-21 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:safemode_project:safemode:*:*:*:*:*:ruby:*:*
More vulnerabilities in Safemode Project Safemode
- CVE-2016-3693 — High (CVSS 8.1): The Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, allows…
All CVEs affecting Safemode Project Safemode →
Other CWE-184 vulnerabilities
- CVE-2026-28363 — Critical (CVSS 9.9): In OpenClaw before 2026.2.23, tools.exec.safeBins validation for sort could be bypassed via GNU long-option…
- CVE-2026-56315 — Critical (CVSS 9.8): picklescan before 1.0.4 fails to block at least seven Python standard library modules (including uuid, _osx_support,…
- CVE-2026-53873 — Critical (CVSS 9.8): picklescan before 1.0.4 contains an incomplete blocklist for the profile module that fails to block the module-level…
- CVE-2025-71323 — Critical (CVSS 9.8): picklescan before 0.0.33 fails to block the ctypes module, allowing attackers to achieve remote code execution by…
- CVE-2025-71320 — Critical (CVSS 9.8): picklescan before 0.0.33 contains an incomplete deny-list that fails to block pydoc.locate and operator.methodcaller…
- CVE-2026-41264 — Critical (CVSS 9.8): Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, the specific…