NVD / CVE Program· CNA TYPO3

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

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.31% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: TYPO3 Extension "Apache Solr for TYPO3 - Enterprise Search" 11.6.6, 12.1.4, 13.1.4.

Low priority for now. Upgrade to TYPO3 Extension "Apache Solr for TYPO3 - Enterprise Search" 11.6.6, 12.1.4, 13.1.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.7 · v4.0—No exploit Fix available

Deserialization

EUVD-2026-65350

Published: Aug 25, 2026
Updated: Sep 17, 2026
EPSS: 0.3% · 24th percentile
CWE: CWE-502

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · TYPO3: 7.7; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (TYPO3). Independent of NVD's CPE analysis and usually ahead of it.

TYPO3 Extension "Apache Solr for TYPO3 - Enterprise Search"
- 13.0.0 and later · before 13.1.4affected · semver
- 12.0.0 and later · before 12.1.4affected · semver
- 11.5.0 and later · before 11.6.6affected · semver

Same product

typo3: all records

Other highest-scoring records for the same primary product.

CVE-2026-56092Broken Access Control in extension "Apache Solr for TYPO3 - Enterprise Search" (solr)
30Monitor
CVE-2026-56096Information Disclosure in extension "Apache Solr for TYPO3 - Enterprise Search" (solr)
25Monitor
CVE-2026-56094Information Disclosure in extension "Apache Solr for TYPO3 - Enterprise Search" (solr)
25Monitor

Published before and after this one in the same product

← EarlierCVE-2026-56093Aug 25, 2026 · Broken Access Control in extension "Apache Solr for TYPO3 - Enterprise Search" (solr)
25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
TYPO3 Extension "Apache Solr for TYPO3 - Enterprise Search"	11.6.6	Vendor (CNA)
TYPO3 Extension "Apache Solr for TYPO3 - Enterprise Search"	12.1.4	Vendor (CNA)
TYPO3 Extension "Apache Solr for TYPO3 - Enterprise Search"	13.1.4	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Rafael Kähmremediation developer
Marc Bastian Heinrichsreporter
EXT:solr team by dkd Internet Service GmbHremediation developer

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-502 · Deserialization of Untrusted Data

CVSS vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

The bug in code

The whole CWE-502 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python

1payload = sock.recv(65536)
2job = pickle.loads(payload)

Fixed

python

1payload = sock.recv(65536)
2if not hmac.compare_digest(sign(payload), header_sig):
3    raise PermissionError("invalid signature")
4job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

Object InjectionCAPEC-586likelihood: Medium · High

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

typo3.org/security/advisory/typo3-ext-sa-2026-025

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records