Skip to main content
VulnerabilityPublished

CVE-2026-115190: mautic/core · Deserialization of Untrusted Data

Affects mautic/coreSource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High · fixed in 7.2.0 : patch mautic/core soon.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 7.2.0, 6.0.10, 5.2.12
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade mautic/core to 7.2.0, 6.0.10 or 5.2.12.

Affected software

ProductAffectedFixed in
mautic/coreAffected
  • >=7.0.0 <7.2.0
Fixed in
  • 7.2.0
mautic/coreAffected
  • >=6.0.0 <6.0.10
Fixed in
  • 6.0.10
mautic/coreAffected
  • >=2.15.2 <5.2.12
Fixed in
  • 5.2.12
Packagistmautic/corepkg:composer/mautic/coreOther threatsAffected
  • >=2.15.2 <5.2.12
  • >=6.0.0 <6.0.10
  • >=7.0.0 <7.2.0
Fixed in
  • 5.2.12
  • 6.0.10
  • 7.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade affected Mautic installations to versions 5.2.12, 6.0.10, or 7.2.0 or later where the vulnerability is fixed. No other mitigations are specified. Patch status is confirmed by fixedVersions in the vendor data.

Description

An insecure deserialization (PHP object injection) vulnerability exists in Mautic's handling of segment filters and custom field properties. Several code paths that read these stored values from the database deserialize them without restricting which PHP classes may be instantiated, instead of using Mautic's safe deserialization helper. An attacker who is able to store a crafted serialized value in these segment filter or custom field properties can cause arbitrary PHP objects to be instantiated when Mautic later processes the data, for example during segment evaluation, contact export, or custom field API requests. Combined with gadget chains available in Mautic's dependencies, this could allow an attacker to execute arbitrary code on the server, read, modify, or delete data stored in the Mautic instance, including contact data, and affect its availability. Exploitation requires high privileges or an existing ability to write to the affected stored data.

References

Community reviews

Loading reviews…