| Version | Supported |
|---|---|
| 3.x.x | ✅ |
| 2.x.x | ✅ |
If you discover a security vulnerability, please do not disclose it publicly through GitHub Issues, Discussions, or pull requests.
Instead, report it privately through one of these channels:
- GitHub private vulnerability reporting (preferred): Report a vulnerability
- Email: see below
Security contact: 0125ses@hanmail.net
Please use the following email subject format when possible:
[Security] Brief vulnerability title
For example:
[Security] XSS vulnerability in editor preview
[Security] Possible HTML injection via paste handler
When reporting a vulnerability, please include as much detail as possible, such as:
- A clear description of the vulnerability
- Type of vulnerability, such as XSS, injection, bypass, or information disclosure
- Steps to reproduce the issue
- Potential impact
- Any suggested fix, if available
We will review the report and respond as soon as possible. You can generally expect an initial response within 7 days.
If the vulnerability is accepted, we will investigate the issue, work on a fix, and coordinate disclosure if needed. Once a fix is available, we may publish a security advisory, release notes, or changelog entry depending on the severity.
We are happy to credit reporters for responsibly disclosed vulnerabilities, unless they prefer to remain anonymous. Public credit will usually be given after the issue has been fixed or safely disclosed.
If you want to notify us publicly that a report has been sent, you may open a GitHub Issue with a general title such as:
[Security] Vulnerability report sent by email
Do not include technical details, reproduction steps, proof-of-concept code, screenshots, payloads, affected locations, or any other sensitive information in the public issue.
If the report is declined, we will explain the reason when possible.
Please avoid sharing vulnerability details publicly until we have had a reasonable amount of time to investigate and address the issue.
- Triage — the report is reproduced and its severity assessed (CVSS where applicable).
- Fix — the fix is developed privately, together with a regression case in the XSS corpus
(
test/unit/core/logic/dom/html.xssCorpus.spec.js) or a dedicated test. - Release — the fix ships as a patch release (see below).
- Disclosure — a GitHub Security Advisory is published for confirmed vulnerabilities, with a CVE requested through GitHub when appropriate, and the release note lists the fix under Security.
- Security fixes are released as a patch version of the latest 3.x minor line, without waiting for the next scheduled release.
- Security patches do not contain breaking changes. If a fix requires a behavior change (e.g. stricter sanitizing), the release note explains how to restore the previous behavior where it is safe to do so.
- Users should stay on the latest 3.x patch version to receive security fixes.