CVE-2011-2686

CVE-2011-2686 is a medium-severity vulnerability in Ruby-lang Ruby with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-310.

Key facts

Description

Ruby before 1.8.7-p352 does not reset the random seed upon forking, which makes it easier for context-dependent attackers to predict the values of random numbers by leveraging knowledge of the number sequence obtained in a different child process, a related issue to CVE-2003-0900. NOTE: this issue exists because of a regression during Ruby 1.8.6 development.

Frequently asked questions

What is CVE-2011-2686?
Ruby before 1.8.7-p352 does not reset the random seed upon forking, which makes it easier for context-dependent attackers to predict the values of random numbers by leveraging knowledge of the number sequence obtained in a different child process, a related issue to CVE-2003-0900. NOTE: this issue exists because of a regression during Ruby 1.8.6 development.
How severe is CVE-2011-2686?
CVE-2011-2686 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2011-2686 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (83rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2011-2686?
CVE-2011-2686 primarily affects Ruby-lang Ruby. In total, 12 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2011-2686?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2011-2686 published?
CVE-2011-2686 was published on 2011-08-05 and last updated on 2026-06-16.

References

Affected products (12)

More vulnerabilities in Ruby-lang Ruby

All CVEs affecting Ruby-lang Ruby →

Other CWE-310 (Cryptographic Issues) vulnerabilities

Browse all CWE-310 (Cryptographic Issues) vulnerabilities →