CVE-2026-115190
Description
A flaw was found in Mautic. Several application components process stored data from the database without restricting which program objects can be created during deserialization (the process of converting stored data back into active objects). An authenticated attacker with high privileges can exploit this vulnerability by storing crafted data within segment filters or custom field properties. When Mautic subsequently processes this data, the attacker can achieve arbitrary code execution on the server, as well as access, modify, or delete sensitive application data.
Statement
This vulnerability is rated as having an Important impact because successful exploitation enables authenticated users to achieve arbitrary code execution and compromise host systems, although it requires elevated access rights to inject malicious payloads. Red Hat products do not package or ship Mautic, so standard Red Hat environments are unaffected by this flaw.
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Application Data; Unexpected State
Attackers can modify unexpected objects or data that was assumed to be safe from modification. Deserialized data or code could be modified without using the provided accessor functions, or unexpected functions could be invoked.
Availability
Technical Impact: DoS: Resource Consumption (CPU)
If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.
Other
Technical Impact: Varies by Context
The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation. One example is attackers using gadget chains to perform unauthorized actions, such as generating a shell.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
