How severe is CVE-2012-2695?

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

Which packages are affected by CVE-2012-2695?

CVE-2012-2695 affects the following packages: activerecord (RubyGems), activerecord (RubyGems), activerecord (RubyGems), activerecord (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2012-2695?

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

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

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

How do I mitigate CVE-2012-2695 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.

How does O3 Security protect against CVE-2012-2695?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2012-2695 can be triaged on real exposure rather than presence alone.

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

Yes. There are 1 known exploit references for CVE-2012-2695, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2012-2695 has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 86th 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-2695?

CVE-2012-2695 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2012-2695 was published on October 24, 2017 and was last updated on January 21, 2025. 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-2695 — activerecord

Fix: rails/rails@62f81f4

CVE-2012-2695 is a SQL Injection vulnerability in activerecord. 1 public exploit reference exists, so weaponization risk is real. A fix is available for activerecord — see the affected versions and patch details below.

activerecord vulnerable to SQL Injection

Published

Oct 24, 2017

Updated

Jan 21, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

4 pkgs affected

💎activerecord💎activerecord💎activerecord💎activerecord

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

The Active Record component in Ruby on Rails efore 2.3.15, 3.0.x before 3.0.14, 3.1.x before 3.1.6, and 3.2.x before 3.2.6 does not properly implement the passing of request data to a where method in an ActiveRecord class, which allows remote attackers to conduct certain SQL injection attacks via nested query parameters that leverage improper handling of nested hashes, a related issue to CVE-2012-2661.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`activerecord`	≥ 3.0.0.beta&&< 3.0.14	3.0.14`bundle update activerecord --conservative`
💎RubyGems	`activerecord`	≥ 3.1.0&&< 3.1.6	3.1.6`bundle update activerecord --conservative`
💎RubyGems	`activerecord`	≥ 3.2.0&&< 3.2.6	3.2.6`bundle update activerecord --conservative`
💎RubyGems	`activerecord`	all versions	2.3.15`bundle update activerecord --conservative`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Active Record component in Ruby on Rails before 3.0.14, 3.1.x before…

groups.google.comNVDAug 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activerecord, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update activerecord to 3.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-2695 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2012-2695 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2012-2695. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 HatLow

Product	Fixed in	Advisory
CloudForms for RHEL 6	`converge-ui-devel-0:1.0.4-1.el6cf`	RHSA-2012:1542
Red Hat Subscription Asset Manager 1.1	`rubygem-actionpack-1:3.0.10-11.el6cf`	RHSA-2013:0154
RHEL 6 Version of OpenShift Enterprise	`graphviz-0:2.26.0-10.el6`	RHSA-2013:0582

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-2695 in your dependencies?

O3 Security finds CVE-2012-2695 across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works