# CVE-2026-113712: Cachet has Stored XSS in Incident Component


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-x397-5hrv-j9m9

## What is CVE-2026-113712?

CVE-2026-113712 is a medium-severity vulnerability in cachethq cachet, published on 20 Oct 2026. 

### Official description

Cachet is an open-source status page system. Versions 2.4.1 and earlier have a stored Cross-Site Scripting (XSS) vulnerability in the incident creation form, allowing an authenticated attacker to inject malicious HTML/JavaScript that executes in the browser of any user who views the status page, potentially leading to session token theft and account takeover. Commits 57b44a8bac0b250b0d5751e93e0349070d14606e and 23adbb88ffa819f92be4a905ff1d812670d980a2 in `cachethq/core` patch the issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

2 open source packages ship an affected version, including cachethq/cachet.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cachethq/cachet` | Packagist | All versions to 2.4.1 | None |
| `cachethq/cachet` | Packagist | All versions to 2.4.1 | None |

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

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

## Is CVE-2026-113712 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113712 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113712 is a medium-severity vulnerability in cachethq cachet, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113712 exists.

Affected packages and fixed versions:
- cachethq/cachet (Packagist): affected all versions up to 2.4.1; no fix listed
- cachethq/cachet (Packagist): affected all versions up to 2.4.1; no fix listed

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-113712/ (Markdown: https://insights.sbomify.com/CVE-2026-113712/index.md)
```

## Sources

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

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