# Magento 2 Community Edition Cryptographic Flaw

Advisory record · `GHSA-c2gg-rrhc-fvvg`

- **Identifiers:** `GHSA-c2gg-rrhc-fvvg` · `CVE-2019-7886` · `PKSA-s1qq-6q1j-9th1` · `PKSA-s2r2-2fn9-rh92`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-330](https://cwe.mitre.org/data/definitions/330.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 24 May 2022
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 May 2022, 16:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `magento/community-edition` (Packagist): affected `>=2.1, <2.1.18 || >=2.2, <2.2.9 || >=2.3, <2.3.2`; fixed in `2.1.18`, `2.2.9`, `2.3.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Magento 2 Community Edition versions from 2.1 before 2.1.18, from 2.2 before 2.2.9, and from 2.3 before 2.3.2 are affected. The source gives few details, but it says a weak mechanism is used to generate initialization vectors in several security-relevant contexts, so an attacker may be able to exploit the resulting weakness in encryption. Upgrade to 2.1.18, 2.2.9, or 2.3.2 or later.

Written 4 Nov 2026.

## 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

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.012, the 68th percentile, on 17 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](https://osv.dev/vulnerability/GHSA-c2gg-rrhc-fvvg)

## Sources

- [GitHub Advisory Database: GHSA-c2gg-rrhc-fvvg](https://github.com/advisories/GHSA-c2gg-rrhc-fvvg)
- [OSV: GHSA-c2gg-rrhc-fvvg](https://osv.dev/vulnerability/GHSA-c2gg-rrhc-fvvg)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-7886>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7886.yaml>
- <https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-33>
- <https://web.archive.org/web/20220121011306/https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-33>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c2gg-rrhc-fvvg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c2gg-rrhc-fvvg/>. Everything for agents: <https://agentprime.io/llms.txt>.
