CVE-2026-56095: Insecure Deserialization in extension "Apache Solr for TYPO3 - Enterprise Search" (solr)

Published Aug 25, 2026

Updated

The extension's indexer passed every field value returned by content object rendering through PHP's unserialize() function when transferring multi-value data for the SOLRCLASSIFICATION, SOLRMULTIVALUE and SOLRRELATION content object types, rather than a safe format. If user-generated content saved in the TYPO3 database can reach an indexed field, this exposes a PHP Object Injection surface.

Affected Software

1 affected component

Apache Solr for TYPO3 - Enterprise Search

Event History

Aug 25, 2026

CVE Published

via MITRE·09:00 AM

Data Sourced

via MITRE·09:00 AM

DescriptionWeakness

Data Sourced

via NVD·09:17 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Who is exposed to this issue?

TYPO3 installations using the Apache Solr for TYPO3 - Enterprise Search extension are exposed when user-generated content stored in the TYPO3 database can reach an indexed field handled as SOLR_CLASSIFICATION, SOLR_MULTIVALUE, or SOLR_RELATION.

What would an attacker need to exploit it?

An attacker would need a way to place data into TYPO3 content that is stored in the database and later processed into one of the affected indexed field types. The vulnerability is a PHP Object Injection surface created when the indexer processes those field values.

CVE-2026-56095: Insecure Deserialization in extension "Apache Solr for TYPO3 - Enterprise Search" (solr)

Affected Software

Event History

Frequently Asked Questions

Who is exposed to this issue?

What would an attacker need to exploit it?

Company

Resources

Contact

Frequently Asked Questions

Who is exposed to this issue?

What would an attacker need to exploit it?