# TYPO3 ke_search XML External Entity Injection

Advisory record · `GHSA-fq39-62gx-8hqx`

- **Identifiers:** `GHSA-fq39-62gx-8hqx` · `CVE-2026-46722` · `PKSA-cy57-p12b-t759`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-611](https://cwe.mitre.org/data/definitions/611.html)
- **Tags:** [XML external entities (XXE)](https://agentprime.io/advisories/tag/xxe.md)
- **Published:** 19 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 May 2026, 12:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `tpwd/ke_search` (Packagist): affected `>=7.0.0, <7.0.1 || >=6.0.0, <6.6.1 || >=5.0.0, <5.6.2 || <4.6.7`; fixed in `7.0.1`, `6.6.1`, `5.6.2`, `4.6.7`

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

- 5.9 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`, from CNA (TYPO3)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0030, the 23rd percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:59 UTC: First seen by agentprime
- 31 Oct 2026, 13:59 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fq39-62gx-8hqx)

## Sources

- [GitHub Advisory Database: GHSA-fq39-62gx-8hqx](https://github.com/advisories/GHSA-fq39-62gx-8hqx)
- [OSV: GHSA-fq39-62gx-8hqx](https://osv.dev/vulnerability/GHSA-fq39-62gx-8hqx)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-46722>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/tpwd/ke_search/CVE-2026-46722.yaml>
- <https://github.com/tpwd/ke_search>
- <https://typo3.org/security/advisory/typo3-ext-sa-2026-011>

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-fq39-62gx-8hqx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fq39-62gx-8hqx/>. Everything for agents: <https://agentprime.io/llms.txt>.
