# CVE-2026-115190: Mautic insecure deserialization in segment filters and custom fields

Source: https://junglewise.ai/threats/cve-2026-115190-an-insecure-deserialization-php-object-injection-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-26. Updated: 2026-10-26  
License: CC BY 4.0 with a link back

CVE-2026-115190 · Severity: high · CVSS 8 · Published 2026-10-26

Mautic is a marketing automation platform that manages customer data and campaign segments. An insecure deserialization vulnerability in how segment filters and custom fields are processed allows attackers with administrative privileges or database write access to execute arbitrary code on the server, steal or modify contact data, or disrupt service availability.

Technologies: [Mautic](https://junglewise.ai/threats/technologies/mautic). Vendors: [Mautic](https://junglewise.ai/threats/vendors/mautic).

## Quick answers

**Is CVE-2026-115190 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-115190 being exploited in the wild.

**How severe is CVE-2026-115190?** High severity, with a CVSS score of 8, published 26 October 2026.

**Which products and versions are affected?** Mautic 2.15.2 to 5.2.11, 6.0.0 to 6.0.9, 7.0.0 to 7.1.x.

**Is there a fix for CVE-2026-115190?** Yes: fixed in 5.2.12, 6.0.10, 7.2.0. Until then: Restrict administrative access and permissions to manage segments, custom fields, and API access to trusted users only. Ensure no untrusted parties have write access to the Mautic database.</anigation>
<parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-26"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-115190 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-115190?** Check whether you run Mautic at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 5.2.12, 6.0.10, 7.2.0

Restrict administrative access and permissions to manage segments, custom fields, and API access to trusted users only. Ensure no untrusted parties have write access to the Mautic database.</anigation>
<parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-26"}]

## Technical details

The vulnerability stems from unsafe PHP unserialization of stored segment filter and custom field data without restricting class instantiation, allowing PHP object injection. Attackers with high privileges or database write access can craft malicious serialized payloads that instantiate arbitrary objects; combined with gadget chains in Mautic's dependencies, this enables remote code execution, data exfiltration, or availability impact during segment evaluation, contact export, or API requests.

## Affected products

- Mautic Mautic 2.15.2 to 5.2.11, 6.0.0 to 6.0.9, 7.0.0 to 7.1.x

## References

- [https://packagist.org/](https://packagist.org/)
- [https://github.com/mautic/mautic/security/advisories/GHSA-5r63-8h35-j3mw](https://github.com/mautic/mautic/security/advisories/GHSA-5r63-8h35-j3mw)

## Related threats

- [Mautic open redirect in form submission endpoint](https://junglewise.ai/threats/cve-2026-115196-an-open-redirect-vulnerability-exists-in-the-public-form)
- [Mautic Stats API broken access control in permission enforcement](https://junglewise.ai/threats/cve-2026-115195-a-broken-access-control-vulnerability-exists-in-the-mautic-stats)
- [Mautic stored XSS in HTML-type custom contact fields](https://junglewise.ai/threats/cve-2026-115193-a-stored-cross-site-scripting-xss-vulnerability-exists-in-the)
- [Mautic SQL injection in dashboard widget API](https://junglewise.ai/threats/cve-2026-115192-an-sql-injection-vulnerability-exists-in-the-dashboard-widget)
- [Mautic SQL injection in contact lookup AJAX endpoint](https://junglewise.ai/threats/cve-2026-115191-a-sql-injection-vulnerability-exists-in-a-contact-lookup-ajax)