How severe is CVE-2015-1426?

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

Which packages are affected by CVE-2015-1426?

CVE-2015-1426 affects the following packages: facter (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2015-1426?

Update facter to 2.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1426 is resolved across your whole dependency graph.

How do I detect CVE-2015-1426 in my RubyGems dependencies?

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2015-1426 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-1426 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-2015-1426?

CVE-2015-1426 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th 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-2015-1426?

CVE-2015-1426 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-1426 published, and has it been updated?

CVE-2015-1426 was published on February 23, 2015 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-2015-1426 — facter

CVE-2015-1426 is a Information Exposure vulnerability in facter. A fix is available for facter — see the affected versions and patch details below.

Puppet Labs Facter allows local users to obtain sensitive Amazon EC2 IAM instance metadata

Also known asGHSA-j436-h7hm-rx46

Published

Feb 23, 2015

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 ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

💎facter

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

Puppet Labs Facter 1.6.0 through 2.4.0 allows local users to obtains sensitive Amazon EC2 IAM instance metadata by reading a fact for an Amazon EC2 node.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`facter`	≥ 1.6.0&&< 2.4.1	2.4.1`bundle update facter --conservative`

Affected Products

2 products · 70 configurations

Application

facterpuppet

32 versions

1.6.01.6.11.6.21.6.31.6.41.6.51.6.61.6.71.6.81.6.91.6.101.6.11

Application

facterpuppetlabs

25 versions

1.6.11.6.21.6.31.6.41.6.51.6.61.6.71.6.81.6.91.6.101.6.111.6.12

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for facter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update facter to 2.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1426 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Puppet Labs Facter 1.6.0 through 2.4.0 allows local users to obtains sensitive Amazon EC2 IAM instance metadata by reading a fact for an Amazon EC2 node.

O3 Security · Impact-Aware SCA

Is CVE-2015-1426 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works