Coordinated Vulnerability Disclosure
Coordinated Disclosure Policy
Security findings discovered during independent research are reported directly to the affected vendor or maintainer so users can be protected before technical details become public.
Standard 90-Day Disclosure Window
- Day 0 — Initial Report: Clear technical report, reproduction steps, affected versions, and remediation notes sent to the vendor's security contact (encrypted via PGP whenever available).
- Days 1–7 — Acknowledgment: Coordination channel confirmed and a permanent HTR identifier is logged without naming the product publicly.
- Patch & CVE Coordination: If the vendor is a CVE Numbering Authority (CNA), CVE assignment is handled through them; otherwise assignment is requested via GitHub Security Advisories or MITRE.
- Day 90 or Patch Release: Once a fix is released—or 90 calendar days elapse without a scheduled patch—the full technical advisory is published. Actively exploited critical flaws may carry an accelerated 7–14 day window; complex architectural fixes may receive a mutually agreed extension.
Publication Principles
- No product names, version numbers, or exploit code are published while coordination is active.
- Unassigned CVE identifiers are never claimed prior to official assignment.
- Unsolicited vulnerability disclosures are completely free of charge and strictly separated from any commercial services or equipment donations.
Good-Faith Research Conduct
Good-Faith Research Conduct
All independent research avoids privacy violations, service degradation, and unauthorized access to third-party user data. Verification stops immediately at the minimum proof required to demonstrate impact.