How to Fix CVE-2026-46722: XXE Vulnerability in Extension "Faceted Search"
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-5779: CWE-284 Improper Access Control in Minerva — CWE-284 Improper Access Control in Minerva
- How to Fix CVE-2026-25457: Critical Vulnerability in Mixtape — Critical Vulnerability in Mixtape
- How to Fix CVE-2026-27202: Path Traversal in GetSimpleCMS-CE , Path Traversal in GetSimpleCMS-CE
- How to Fix CVE-2026-4911: CWE-472 External Control of Assumed-Immutable Web Parameter in Booking Package , CWE-472 External Control of Assumed-Immutable Web Parameter in Booking Package
- How to Fix CVE-2026-31224: Deserialization RCE in n/a , Deserialization RCE in n/a
*By Sai Kiran Pandrala*
| Severity | CVSS 5.9 - Medium |
|---|---|
| Actively exploited? | Not currently listed in CISA KEV |
| Affected | 7.0.0 < 7.0.1, 6.0.0 < 6.6.1, 0 < 5.6.2 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-611: Improper Restriction of XML External Entity Reference |
What is CVE-2026-46722?
CVE-2026-46722 is an XML external entity (XXE) flaw in Extension "Faceted Search". The XML parser resolves external entities, which lets an attacker read files on the server or trigger server-side requests. Vendor 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.
Why this CVE matters
XXE vulnerabilities convert a simple XML parsing endpoint into a file-read and server-side request forgery primitive. The chained impact is often cloud-metadata theft or internal service enumeration from inside the target's network.
For deployments of Extension "Faceted Search" that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.
Am I affected?
You are affected if your installation matches any of these version ranges:
- Extension "Faceted Search": 7.0.0 < 7.0.1
- Extension "Faceted Search": 6.0.0 < 6.6.1
- Extension "Faceted Search": 0 < 5.6.2
Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.
Open Extension "Faceted Search"'s About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.
How to fix CVE-2026-46722
- Read the vendor advisory in full: https://typo3.org/security/advisory/typo3-ext-sa-2026-011
- Upgrade Extension "Faceted Search" to the patched build listed in the vendor advisory.
- Back up the configuration (and database, where applicable) before upgrading.
- Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
- Restart the affected service so the patched binary loads, then verify the new version (see verification section).
Upgrade typo3 extension "faceted search"
# CVE-2026-46722 affects Extension "Faceted Search" 7.0.0 < 7.0.1.
# Fixed in 7.0.1. Vendor advisory: https://typo3.org/security/advisory/typo3-ext-sa-2026-011
# 1. Identify the running version using the vendor-documented command.
# (Open the product UI -> About, or run the CLI version probe.)
# 2. Stage the patched build named in the advisory.
# Vendor advisory: https://typo3.org/security/advisory/typo3-ext-sa-2026-011
# 3. Apply the upgrade. If the vendor ships a Linux package, pull it via your
# distribution's package manager:
sudo apt update && sudo apt install --only-upgrade extension--faceted-search # Debian / Ubuntu
sudo dnf upgrade extension--faceted-search # RHEL / Rocky / Alma / Fedora
# 4. Restart the affected service so the new binary loads.
sudo systemctl restart extension--faceted-search 2>/dev/null || true
# 5. Re-run the version probe and confirm it matches 7.0.1.
# Windows-hosted installs of Extension "Faceted Search": apply via PSWindowsUpdate or the vendor MSI.
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Get-WindowsUpdate -AcceptAll -Install -AutoReboot
Verify the fix landed
# CVE-2026-46722 verification checklist.
# 1. Confirm the running version matches 7.0.1 (replace the version probe with
# the platform-specific command shown above).
# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
# OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-46722.
# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"
# 4. Cross-check the running build against the vendor advisory:
# https://typo3.org/security/advisory/typo3-ext-sa-2026-011
If you cannot patch immediately
Disable XML external entity processing in the affected component if the vendor documents a configuration toggle. Otherwise, patch.
How to verify the fix worked
- After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
- Confirm the patched build matches the version listed in the vendor advisory.
- Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-46722.
- Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
- Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.
If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.
Frequently asked questions
Is CVE-2026-46722 being exploited in the wild?
Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.
Will a WAF or IDS rule fully mitigate CVE-2026-46722?
No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.
How long should I plan for the upgrade?
Typical vendor-documented upgrade windows for Extension "Faceted Search" run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.
References
- Official vendor advisory: https://typo3.org/security/advisory/typo3-ext-sa-2026-011
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-46722
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*