# CVE-2026-115196: An Open Redirect vulnerability exists in the public form submission endpoint (/form/submit) of Mautic.


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-5mm3-3g7p-9868

## What is CVE-2026-115196?

CVE-2026-115196 is a medium-severity vulnerability, published on 26 Oct 2026. 

### Official description

An Open Redirect vulnerability exists in the public form submission endpoint (/form/submit) of Mautic. After a form is submitted, the application redirects the visitor to a return address supplied with the submission without verifying that it points to the Mautic instance or another trusted host. An unauthenticated attacker can exploit this to send visitors from a legitimate Mautic domain to an arbitrary external website, for example to phishing pages that imitate the original landing page or to sites that deliver malware. Any Mautic instance with a published form is affected. Exploitation requires the victim to submit a form prepared by the attacker.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2026-115196 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115196 is a medium-severity vulnerability, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115196 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-115196/ (Markdown: https://insights.sbomify.com/CVE-2026-115196/index.md)
```

## Sources

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

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