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

Q: How do I fix CVE-2016-3693?

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

Q: Is CVE-2016-3693 being exploited?

CVE-2016-3693 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-2016-3693 affect?

CVE-2016-3693 affects safemode. Severity is 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 context-dependent attackers to obtain sensitive information via the inspect method.

Q: How urgent is CVE-2016-3693?

Priority 54/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.1REMOTEUPGRADE

CVE-2016-3693 is a high-severity flaw (CVSS 8.1) affecting safemode. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, allows context-dependent attackers to obtain sensitive information via the inspect method.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	2.1% (top 18%)
CISA exploited list	No
Weakness	CWE-200, CWE-264
Published	2016-05-20
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

2016-05-20 14:59 UTCPublished CVE record published
2026-06-17 00:46 UTCUpdated Record last modified

safemode project safemode UPGRADE

Affected: <= 1.2.3

Fixed in: newer than 1.2.3

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.2.3 (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-2016-3693?

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

Is CVE-2016-3693 being exploited?

CVE-2016-3693 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-2016-3693 affect?

CVE-2016-3693 affects safemode. Severity is 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 context-dependent attackers to obtain sensitive information via the inspect method.

How urgent is CVE-2016-3693?

Priority 54/100. High severity; Remotely exploitable, no login, no user action

Software pages

Ruby on Rails vulnerabilities · Ruby vulnerabilities

Related CVEs

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

References

← Back to latest CVEs