# ZendFramework Potential Information Disclosure and Insufficient Entropy vulnerabilities

Advisory record · `GHSA-xg9w-r469-m455`

- **Identifiers:** `GHSA-xg9w-r469-m455` · `PKSA-n4jn-zfz3-4hxy`
- **State:** Confirmed
- **Severity:** CVSS 7.4 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:** 7 Jun 2024
- **Updated:** 4 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Jun 2024, 20:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `zendframework/zendframework` (Packagist): affected `>=2.0.0, <2.0.8 || >=2.1.0, <2.1.4`; fixed in `2.0.8`, `2.1.4`

## Machine-written summary

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

> Zend Framework zendframework/zendframework versions 2.0.0 before 2.0.8 and 2.1.0 before 2.1.4 are affected. When OpenSSL and Mcrypt are unavailable, the Zend\Math\Rand component falls back to PHP's mt_rand(), whose output an attacker can predict by recovering the seed, and the Zend\Validate\Csrf component can leak a random number that exposes that seed. The source gives few details on the exact preconditions. Upgrade to version 2.0.8 or 2.1.4, 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.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:28 UTC: First seen by agentprime
- 31 Oct 2026, 14:28 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xg9w-r469-m455)

## Sources

- [GitHub Advisory Database: GHSA-xg9w-r469-m455](https://github.com/advisories/GHSA-xg9w-r469-m455)
- [OSV: GHSA-xg9w-r469-m455](https://osv.dev/vulnerability/GHSA-xg9w-r469-m455)
- <https://github.com/zendframework/zendframework/commit/6975695dfdb201bda0aea02bcc11b4a85ddc89fa>
- <https://github.com/zendframework/zendframework/commit/97b98e7208f93613ab358432e56b6e2245153807>
- <https://framework.zend.com/security/advisory/ZF2013-02>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/zendframework/zendframework/ZF2013-02.yaml>
- <https://github.com/zendframework/zendframework>

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-xg9w-r469-m455>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xg9w-r469-m455/>. Everything for agents: <https://agentprime.io/llms.txt>.
