Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Magento 2 Community Edition versions 2.1.0 to before 2.1.18, 2.2.0 to before 2.2.9, and 2.3.0 to before 2.3.2 use a cryptographically weak pseudo-random number generator in several security-relevant contexts. The source gives few details on how an attacker could exploit this or what they could gain. Upgrade to Magento 2 Community Edition 2.1.18, 2.2.9, or 2.3.2, depending on the release line in use. No workaround is listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.012, the 68th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:32 UTC First seen by agentprime
- 31 Oct 2026, 14:32 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8v9h-m7pj-hx7c
- OSV: GHSA-8v9h-m7pj-hx7c
- nvd.nist.gov/vuln/detail/CVE-2019-7860
- github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7860.yaml
- github.com/magento/magento2
- magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-33
- web.archive.org/web/20220121011306/https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-33