# CVE-2026-115190: An insecure deserialization (PHP object injection) vulnerability exists in Mautic's handling of segment filters and custom field properties.


- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-5r63-8h35-j3mw

## What is CVE-2026-115190?

CVE-2026-115190 is a high-severity vulnerability, published on 26 Oct 2026. 

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-115190?


## How do I fix CVE-2026-115190?

No fix has been published for CVE-2026-115190 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115190 being exploited?

There is no known exploitation of CVE-2026-115190 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115190 and fix it if it is affected.

What it is: CVE-2026-115190 is a high-severity vulnerability, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115190 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115190/ (Markdown: https://insights.sbomify.com/CVE-2026-115190/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115190
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115190
- OSV: https://osv.dev/vulnerability/CVE-2026-115190

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115190/
Summaries are generated and may contain mistakes; the official description above is the record.