Quick answers
- Is CVE-2026-115194 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115194 being exploited in the wild.
- How severe is CVE-2026-115194?
- Medium severity, with a CVSS score of 6.5, published 26 October 2026.
- Which products and versions are affected?
- Mautic Core >= 2.3.0 < 5.2.12, >= 6.0.0 < 6.0.10, >= 7.0.0 < 7.2.2.
- Is there a fix for CVE-2026-115194?
- Yes: fixed in 5.2.12, 6.0.10, 7.2.2. Until then: Disable API access or restrict asset creation permissions to trusted administrative users. Review existing local assets for file paths outside the asset upload directory. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115194 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-115194?
- Check whether you run Mautic Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 5.2.12, 6.0.10, 7.2.2
Disable API access or restrict asset creation permissions to trusted administrative users. Review existing local assets for file paths outside the asset upload directory.
Technical details
A path traversal vulnerability in the Mautic Asset API fails to restrict the file path when creating local assets through the API. An authenticated user with asset creation permissions can register arbitrary files readable by the web server process as assets. When published, the asset's public download URL serves the file contents without authentication, allowing arbitrary file read.
Affected products
- Mautic Core >= 2.3.0 < 5.2.12, >= 6.0.0 < 6.0.10, >= 7.0.0 < 7.2.2
Timeline
- 2026-10-26: disclosed