What is CVE-2026-56095?

CVE-2026-56095 is Insecure Deserialization in extension "Apache Solr for TYPO3 - Enterprise Search" (solr). The supplied enrichment data classifies it as Deserialization mapped to CWE-502 Deserialization of Untrusted Data.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-56095. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-56095 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

2 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-56095 using CVSS 7.7, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highDeserializationpublic exploit

CVE-2026-56095

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

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 SOLR_CLASSIFICATION, SOLR_MULTIVALUE and SOLR_RELATION 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.

Published Aug 25, 2026Updated Aug 25, 2026Sources: NVD, TYPO3 (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

TYPO3

3 products listed

CVSS base

7.7

high

Remediation

The vendor's own words where we have them.

Upgrade Extension "Apache Solr for TYPO3 - Enterprise Search" to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
TYPO3	Extension "Apache Solr for TYPO3 - Enterprise Search"	13.0.0 to < 13.1.4	Vulnerable
TYPO3	Extension "Apache Solr for TYPO3 - Enterprise Search"	12.0.0 to < 12.1.4	Vulnerable
TYPO3	Extension "Apache Solr for TYPO3 - Enterprise Search"	0 to < 11.6.6	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack Complexity

High

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.7	CVSS 4.0	high	—	—	TYPO3 (CNA)

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-502 · Deserialization of Untrusted Data

Modify Application Data
Unexpected State
DoS: Resource Consumption (CPU)
Varies by Context

Mitigation: If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.

Weakness & attack patterns

CWE-502Deserialization of Untrusted Data

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-586 · Object Injection

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Extension "Apache Solr for TYPO3 - Enterprise Search".
Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.7 (AV:N)
Aug 25, 2026 · NVD
Initial · CVE published
Aug 25, 2026 · NVD
Added · GHSA-r2vh-j53r-xpr5 published (high)
Aug 25, 2026 · GitHub Security Advisory

References

3 on the record

typo3.org/security/advisory/typo3-ext-sa-2026-025
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-56095
NVD
github.com/advisories/GHSA-r2vh-j53r-xpr5
Exploit, Third Party Advisory

Elsewhere on this site

TYPO3every CVE for this vendor
Deserializationsame class
CWE-502other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-56095 is Insecure Deserialization in extension "Apache Solr for TYPO3 - Enterprise Search" (solr), a high vulnerability affecting Extension "Apache Solr for TYPO3 - Enterprise Search" from TYPO3. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-56095. Public exploit evidence is: 2 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.