# CVE-2026-46722: XML External Entity Injection in extension "Faceted Search" (ke_search)


- **Severity:** Medium 5.9 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 19 May 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-fq39-62gx-8hqx

## What is CVE-2026-46722?

CVE-2026-46722 is a medium-severity vulnerability in TYPO3 Extension "Faceted Search", published on 19 May 2026. 

### Official description

The OOXML parsing of the file indexer does not disable external entity resolution. A crafted xlsx or pptx document placed in an indexed directory can cause local files to be read or outbound HTTP requests to be performed, with the retrieved content being written to the search index.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2026-46722?

8 open source packages ship an affected version, including tpwd/ke_search.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tpwd/ke_search` | Packagist | All versions | 4.6.7 |
| `tpwd/ke_search` | Packagist | All versions | 4.6.7 |
| `tpwd/ke_search` | Packagist | From 5.0.0 | 5.6.2 |
| `tpwd/ke_search` | Packagist | From 5.0.0 | 5.6.2 |
| `tpwd/ke_search` | Packagist | From 6.0.0 | 6.6.1 |
| `tpwd/ke_search` | Packagist | From 6.0.0 | 6.6.1 |
| `tpwd/ke_search` | Packagist | From 7.0.0 | 7.0.1 |
| `tpwd/ke_search` | Packagist | From 7.0.0 | 7.0.1 |

## How do I fix CVE-2026-46722?

Upgrade tpwd/ke_search to a fixed version for your release line: 4.6.7, 5.6.2, 6.6.1 or 7.0.1.

## Is CVE-2026-46722 being exploited?

There is no known exploitation of CVE-2026-46722 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46722 and fix it if it is affected.

What it is: CVE-2026-46722 is a medium-severity vulnerability in TYPO3 Extension "Faceted Search", published on 19 May 2026. 
Exploitation: There is no known exploitation of CVE-2026-46722 in the wild and no public exploit code.

Affected packages and fixed versions:
- tpwd/ke_search (Packagist): affected all versions; fixed in 4.6.7
- tpwd/ke_search (Packagist): affected all versions; fixed in 4.6.7
- tpwd/ke_search (Packagist): affected from 5.0.0; fixed in 5.6.2
- tpwd/ke_search (Packagist): affected from 5.0.0; fixed in 5.6.2
- tpwd/ke_search (Packagist): affected from 6.0.0; fixed in 6.6.1
- tpwd/ke_search (Packagist): affected from 6.0.0; fixed in 6.6.1
- tpwd/ke_search (Packagist): affected from 7.0.0; fixed in 7.0.1
- tpwd/ke_search (Packagist): affected from 7.0.0; fixed in 7.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46722/ (Markdown: https://insights.sbomify.com/CVE-2026-46722/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46722
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46722
- OSV: https://osv.dev/vulnerability/CVE-2026-46722

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46722/
Summaries are generated and may contain mistakes; the official description above is the record.