# CVE-2026-8080: MISP core - Stored XSS in MISP template (old engine) element attribute type

> Stored XSS in MISP old template engine allows attackers with template modification rights to execute scripts in victim browsers.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-3v62-pvrh-853r

## What is CVE-2026-8080?

CVE-2026-8080 is a medium-severity cross-site scripting vulnerability in Misp-Project Misp, published on 7 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in misp allows Stored XSS.

This issue affects MISP before 2.5.37.

A stored cross-site scripting vulnerability exists in the template element attribute handling logic. The application accepted arbitrary values for the TemplateElementAttribute type and category fields without validating them against the known MISP attribute type and category definitions. An attacker with permission to create or modify template element attributes could store a crafted type value.

This affects the old templating (not more accessible in 2.5.37) engine from MISP which will be removed in 2.5.38

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

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

It affects 1 product.


Products: Misp-Project Misp.

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

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

## Is CVE-2026-8080 being exploited?

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

Public exploit code:

- https://github.com/George0Papasotiriou/CVE-2026-8080-DKIM-Signature-Verification-Bypass-Header-Canonicalization-Flaw- (github_poc): https://github.com/George0Papasotiriou/CVE-2026-8080-DKIM-Signature-Verification-Bypass-Header-Canonicalization-Flaw-

## Other vulnerabilities in Misp-Project Misp

- [CVE-2024-46918](https://insights.sbomify.com/CVE-2024-46918/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-45509](https://insights.sbomify.com/CVE-2024-45509/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-29858](https://insights.sbomify.com/CVE-2024-29858/): File upload in n/a (critical 9.8)
- [CVE-2024-29859](https://insights.sbomify.com/CVE-2024-29859/): File upload in n/a (critical 9.8)
- [CVE-2024-25674](https://insights.sbomify.com/CVE-2024-25674/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8080 is a medium-severity cross-site scripting vulnerability in Misp-Project Misp, published on 7 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-8080 in the wild and no public exploit code.

Affected product: Misp-Project Misp. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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