Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-7954

rubygem-bundler: Code execution via gem name collision in bundler

Overview

Published
22 Dec 2016
Modified
17 Jun 2026
Critical CVE
1 Registry packages
9 OS packages
3 Linux distributions
Yes Fix available

Description

Bundler 1.x might allow remote attackers to inject arbitrary Ruby code into an application by leveraging a gem name collision on a secondary source. NOTE: this might overlap CVE-2013-0334.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-94

Affected packages · 1

Packages affected by CVE-2016-7954
EcosystemPackageVulnerableFixed in
RubyGems bundler >=1.0.0, <2.0.0 2.0.0

Open a package to see all its vulnerabilities.

Operating systems · 4 fixes

Red Hat 1 release · 1 package

wont fix 1
rh-ruby22-rubygem-bundler
Red Hat fixes for CVE-2016-7954
ReleasePackageFixed in
7 rh-ruby22-rubygem-bundler +7 wont fix

debian 2 releases · 1 package

affected 2
bundler
debian fixes for CVE-2016-7954
ReleasePackageFixed in
10 bundler affected
9 bundler affected

ubuntu 1 release · 1 package

affected 1
bundler
ubuntu fixes for CVE-2016-7954
ReleasePackageFixed in
18.04-ESM bundler affected

References

Show all 27 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.