Which versions of facter are affected by CVE-2015-1426?

facter (rubygems) versions >= 1.6.0, < 2.4.1 is affected.

Is there a fix for CVE-2015-1426?

Yes. CVE-2015-1426 is fixed in 2.4.1. Upgrade to this version or later.

Is CVE-2015-1426 exploitable, and should I be worried?

Whether CVE-2015-1426 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2015-1426 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2015-1426 in facter

Q: What is CVE-2015-1426?

CVE-2015-1426 is a low-severity security vulnerability in facter (rubygems), affecting versions >= 1.6.0, < 2.4.1. It is fixed in 2.4.1.

Q: Is there a fix for CVE-2015-1426?

Yes. CVE-2015-1426 is fixed in 2.4.1. Upgrade to this version or later.

Q: Is CVE-2015-1426 exploitable, and should I be worried?

Whether CVE-2015-1426 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2015-1426 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2015-1426?

Upgrade facter to 2.4.1 or later.

CVE-2015-1426

CVE-2015-1426 is a low-severity security vulnerability in facter (rubygems), affecting versions >= 1.6.0, < 2.4.1. It is fixed in 2.4.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

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.

Impact

Affected versions

facter (>= 1.6.0, < 2.4.1)

Security releases

facter → 2.4.1 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade facter to 2.4.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2015-1426? CVE-2015-1426 is a low-severity security vulnerability in facter (rubygems), affecting versions >= 1.6.0, < 2.4.1. It is fixed in 2.4.1.
Which versions of facter are affected by CVE-2015-1426? facter (rubygems) versions >= 1.6.0, < 2.4.1 is affected.
Is there a fix for CVE-2015-1426? Yes. CVE-2015-1426 is fixed in 2.4.1. Upgrade to this version or later.
Is CVE-2015-1426 exploitable, and should I be worried? Whether CVE-2015-1426 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2015-1426 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2015-1426? Upgrade facter to 2.4.1 or later.

Other vulnerabilities in facter

CVE-IDSeverityPackage summary

CVE-2014-3248Mediumfacter: facter, hiera, mcollective-client, and puppet affected by untrusted search path vulnerability