Report a security vulnerability

A single entry point for every MoX project (moxsh-terminal, moxsh-proot, moxwebgpu, agent-core, moxsh-plugins, moxsh-suite, mox-site, mox-id). No need to dig through six SECURITY.md files, and no GitHub account required — this form supports fully anonymous reports.

Never post vulnerability details in public Issues, Discussions or chat groups.
Submitted over HTTPS and written only to a server-side database, the report is readable in cleartext by administrators in the admin console after authentication — no encryption for you, no decryption for us, and nothing exposed to the browser. For a directly exploitable 0day, describe impact and reproduction steps only; send full exploit code separately after we confirm a channel.
Code-of-conduct complaints are not vulnerabilities. Use the separate conduct complaint form; the two queues are deliberately kept apart.

Submission channels

Anonymous form belowRecommended. No account and no encryption needed. You immediately receive a one-time ticket to check progress. IP rate limiting and human verification block bulk abuse.
GitHub private reportingSecurity → Report a vulnerability on each public repo. Requires a GitHub account, but feeds directly into a GitHub Security Advisory and can be linked to a CVE.
Contact emailRevealed after sign-in on the homepage Contact section. For general correspondence only — prefer this form for vulnerability details so they are not left in a mailbox.

Why no encryption is required

We deliberately do not use PGP: encrypted reports force the maintainer to decrypt every submission before reading it in the admin console, which slows triage and makes reports easy to miss. Instead we constrain both transport and access:

If your organisation mandates end-to-end encryption, use GitHub private vulnerability reporting or contact us by email to agree on a separate channel.

Coordinated disclosure

AcknowledgementUsually within 72 hours; holidays and travel may delay it. This is a target, not a hard SLA.
Fix timelineUsually an initial assessment and plan within 3 days of acknowledgement; high severity first.
EmbargoDefault 30 days from the release containing the fix. Neither side publishes details during this window; ask if you need an extension.
90-day fallbackIf no fix and no reasonable explanation within 90 days of acknowledgement, you may publish without objection from us.
CVEThe maintainer decides whether to request one; reporters can be credited as discoverers. We do not accept paid disclosure conditioned on a CVE.
CreditNamed in the CHANGELOG and the hall of fame below on release (anonymous or pseudonymous on request), including low-severity and duplicate reports unless declined.
NotificationAnnounced via GitHub Security Advisories, Release Notes and the status page; CLI and App update checks surface security upgrades where available.

Supported versions

These projects move fast: only the latest release on each repo's default branch is maintained. Older versions receive no separate patches — upgrading is the fix. Version numbers live in each repo's Releases, package.json or Cargo.toml; we deliberately do not freeze them on this page.

Threat model: what counts

Anonymous report form

The response contains only a one-time ticket — no body echo, nothing published on any public page.
Save your ticket: the server stores only its hash, so a lost ticket cannot be recovered.
Preparing verification…

Check progress

Hall of fame

No publicly credited reports yet. After a fix ships, reporters are listed here as they prefer (anonymous or pseudonymous).

Historical advisories

See each repo's GitHub Security Advisories and Releases; this page does not duplicate a list that would go stale.