CVE-2017-7540: rubygem-safemode, as used in Foreman, versions 1.3.2 and earlier are vulnerable to bypassing safe mode limitat

Q: How do I fix CVE-2017-7540?

safemode: upgrade to newer than 1.3.2. Exact commands for each OS are on this page.

Q: Is CVE-2017-7540 being exploited?

CVE-2017-7540 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-7540 affect?

CVE-2017-7540 affects safemode. Severity is critical (CVSS 9.8). 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

Q: How urgent is CVE-2017-7540?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2017-7540 is a critical-severity flaw (CVSS 9.8) affecting safemode. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Weakness	CWE-184
Published	2017-07-21
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: safemode project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-07-21 22:29 UTCPublished CVE record published
2026-06-17 01:24 UTCUpdated Record last modified

safemode project safemode UPGRADE

Affected: <= 1.3.2

Fixed in: newer than 1.3.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy safemode || rpm -q safemode || safemode --version

2. UPGRADE to newer than 1.3.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade safemode

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade safemode

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-7540?

safemode: upgrade to newer than 1.3.2. Exact commands for each OS are on this page.

Is CVE-2017-7540 being exploited?

CVE-2017-7540 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-7540 affect?

CVE-2017-7540 affects safemode. Severity is critical (CVSS 9.8). 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

How urgent is CVE-2017-7540?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Ruby vulnerabilities

Related CVEs

CVE-2016-3693 HIGH 8.1 UPGRADE The Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, al

References

← Back to latest CVEs