How severe is CVE-2012-2126?

No CVSS score has been assigned to CVE-2012-2126 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-2126?

CVE-2012-2126 affects the following packages: rubygems-update (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2012-2126?

Update rubygems-update to 1.8.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-2126 is resolved across your whole dependency graph.

How do I detect CVE-2012-2126 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rubygems-update, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-2126 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2012-2126 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-2126 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-2126?

CVE-2012-2126 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-2126?

CVE-2012-2126 is classified as CWE-310 (CWE-310). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-2126 published, and has it been updated?

CVE-2012-2126 was published on October 1, 2013 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

CVE-2012-2126 — rubygems-update

Fix: rubygems/rubygems@d4c7eaf

CVE-2012-2126 is a CWE-310 vulnerability in rubygems-update. A fix is available for rubygems-update — see the affected versions and patch details below.

RubyGems does not verify SSL certificate

Also known asGHSA-5mgj-mvv8-46mw

Published

Oct 1, 2013

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

💎rubygems-update

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

RubyGems before 1.8.23 does not verify an SSL certificate, which allows remote attackers to modify a gem during installation via a man-in-the-middle attack.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`rubygems-update`	all versions	1.8.23`bundle update rubygems-update --conservative`

Affected Products

1 product · 23 configurations

Application

rubygemsrubygems

≤ 1.8.22

22 versions

1.8.01.8.11.8.21.8.31.8.41.8.51.8.61.8.71.8.81.8.91.8.101.8.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rubygems-update, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rubygems-update to 1.8.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-2126 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

The Red Hat Security Response Team has rated this issue as having moderate security impact in CloudForms 1.1. This issue is not currently planned to be addressed in future updates.

Product	Fixed in	Advisory
Red Hat Enterprise Linux 6	`rubygems-0:1.3.7-4.el6_4`	RHSA-2013:1441
Red Hat Enterprise MRG 2	`cumin-0:0.1.5787-4.el6`	RHSA-2013:1852
RHEL 6 Version of OpenShift Enterprise 1.2	`rubygems-0:1.8.24-4.el6op`	RHSA-2013:1203

Frequently Asked Questions

RubyGems before 1.8.23 does not verify an SSL certificate, which allows remote attackers to modify a gem during installation via a man-in-the-middle attack.

O3 Security · Impact-Aware SCA

Is CVE-2012-2126 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works