What is CVE-2026-0895?

CVE-2026-0895 is a medium-severity insecure deserialization vulnerability in cpsit/typo3-mailqueue (composer), affecting versions < 0.4.3. It is fixed in 0.4.3, 0.5.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

Which versions of cpsit/typo3-mailqueue are affected by CVE-2026-0895?

cpsit/typo3-mailqueue (composer) versions < 0.4.3 is affected.

Is there a fix for CVE-2026-0895?

Yes. CVE-2026-0895 is fixed in 0.4.3, 0.5.1. Upgrade to this version or later.

Is CVE-2026-0895 exploitable, and should I be worried?

Whether CVE-2026-0895 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-0895 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-0895 in cpsit/typo3-mailqueue | Intelligent Application Security

Q: Which versions of cpsit/typo3-mailqueue are affected by CVE-2026-0895?

cpsit/typo3-mailqueue (composer) versions < 0.4.3 is affected.

Q: Is there a fix for CVE-2026-0895?

Yes. CVE-2026-0895 is fixed in 0.4.3, 0.5.1. Upgrade to this version or later.

Q: Is CVE-2026-0895 exploitable, and should I be worried?

Whether CVE-2026-0895 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-0895 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-0895?

Upgrade: cpsit/typo3-mailqueue to 0.4.3 or later, cpsit/typo3-mailqueue to 0.5.1 or later.

Summary

Description

The extension extends TYPO3’s FileSpool component, which was vulnerable to Insecure Deserialization prior to TYPO3-CORE-SA-2026-004. Since the related fix is overwritten by the extension, using the extension with a patched TYPO3 core version still allows for Insecure Deserialization, because the affected vulnerable code was extracted from TYPO3 core to the extension.

More information about this vulnerability can be found in the related TYPO3 Core Security Advisory TYPO3-CORE-SA-2026-004.

References

Impact

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

Affected versions

cpsit/typo3-mailqueue (< 0.4.3) cpsit/typo3-mailqueue (>= 0.5.0, < 0.5.1)

Security releases

cpsit/typo3-mailqueue → 0.4.3 (composer) cpsit/typo3-mailqueue → 0.5.1 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

cpsit/typo3-mailqueue to 0.4.3 or later; cpsit/typo3-mailqueue to 0.5.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-0895? CVE-2026-0895 is a medium-severity insecure deserialization vulnerability in cpsit/typo3-mailqueue (composer), affecting versions < 0.4.3. It is fixed in 0.4.3, 0.5.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
Which versions of cpsit/typo3-mailqueue are affected by CVE-2026-0895? cpsit/typo3-mailqueue (composer) versions < 0.4.3 is affected.
Is there a fix for CVE-2026-0895? Yes. CVE-2026-0895 is fixed in 0.4.3, 0.5.1. Upgrade to this version or later.
Is CVE-2026-0895 exploitable, and should I be worried? Whether CVE-2026-0895 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-0895 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-0895?
- Upgrade cpsit/typo3-mailqueue to 0.4.3 or later
- Upgrade cpsit/typo3-mailqueue to 0.5.1 or later

Other vulnerabilities in cpsit/typo3-mailqueue

CVE-2026-0895