# CVE-2026-115194: A path traversal vulnerability exists in the Mautic Asset API.


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-wfhm-289v-79vp

## What is CVE-2026-115194?

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

### Official description

A path traversal vulnerability exists in the Mautic Asset API. When creating a local asset through the API, the supplied file path is not restricted to the asset upload directory. An authenticated API user with permission to create assets can register any file that is readable by the web server process as a Mautic asset. When the asset is published, its public download URL serves the contents of that file without authentication. This allows the attacker to read arbitrary files from the server, including Mautic configuration files containing the database password, secret key, and mail (SMTP) credentials, as well as system files and any other file readable by the web server user. Exposed credentials can be used to access the database or other connected services, and anyone with the public asset URL can retrieve the file contents.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-115194 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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