How severe is GHSA-j436-h7hm-rx46?

No CVSS score has been assigned to GHSA-j436-h7hm-rx46 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j436-h7hm-rx46?

GHSA-j436-h7hm-rx46 affects the following packages: facter (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-j436-h7hm-rx46?

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

How do I detect GHSA-j436-h7hm-rx46 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 GHSA-j436-h7hm-rx46 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 GHSA-j436-h7hm-rx46 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j436-h7hm-rx46 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 GHSA-j436-h7hm-rx46?

GHSA-j436-h7hm-rx46 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th 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 GHSA-j436-h7hm-rx46?

GHSA-j436-h7hm-rx46 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 GHSA-j436-h7hm-rx46 published, and has it been updated?

GHSA-j436-h7hm-rx46 was published on May 14, 2022 and was last updated on December 4, 2024. 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

Puppet Labs Facter allows local users to obtain sensitive Amazon EC2 IAM instance metadataGHSA-j436-h7hm-rx46

GHSA-j436-h7hm-rx46 is a Information Exposure vulnerability in facter. A fix is available for facter — see the affected versions and patch details below.

Also known asCVE-2015-1426

Published

May 14, 2022

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 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 CVEs30th percentile — riskier than 30% 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 GHSA-j436-h7hm-rx46 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 GHSA-j436-h7hm-rx46 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works