Quick answers
- Is CVE-2026-102927 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102927 being exploited in the wild.
- How severe is CVE-2026-102927?
- Informational severity, published 5 November 2026.
- Which products and versions are affected?
- HedgeDoc before 1.11.1.
- Is there a fix for CVE-2026-102927?
- Yes: fixed in 1.11.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102927 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-102927?
- Check whether you run HedgeDoc 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: 1.11.1
Technical details
The WebSocket permission handler in HedgeDoc prior to 1.11.1 fails to validate that permission values are within the set of allowed values (freely, editable, limited, locked, protected, private), allowing a note owner to submit arbitrary permission strings. The viewing and editing permission checks only handle known values and fall through to permissive defaults for unknown values. SQLite can persist invalid values because the database column lacks strict enforcement, while MySQL and PostgreSQL reject updates but leave in-memory state inconsistent.
Affected products
- HedgeDoc HedgeDoc before 1.11.1
Timeline
- 2026-11-05: disclosed