Report a vulnerability
Report a suspected Registry Stack vulnerability privately. Never open a public issue or pull request for a suspected credential disclosure, auth bypass, audit redaction failure, source connector data leakage, or signing-key handling bug.
When to use this
Section titled “When to use this”Use the private disclosure channel for anything in scope on this page. If you are unsure whether a behavior is exploitable, report it privately. Use a public product issue only for a known, non-exploitable gap that does not include sensitive reproduction details.
Before you start
Section titled “Before you start”Gather what the report needs before you open the channel:
- The affected commit or release tag.
- The config shape involved (redact secret values before you paste anything).
- Reproduction steps.
- The impact you observed or expect.
Do not include live credentials, bearer tokens, API keys, private keys, or raw registry records in the report.
- Report privately through GitHub Security Advisories.
- If GitHub Security Advisories is unavailable, contact the maintainer through an existing private project channel instead of opening a public issue or pull request.
- Include the affected commit, config shape, reproduction steps, and impact from the Before you start checklist.
Registry Stack aims to acknowledge private reports within 5 business days.
What is in scope
Section titled “What is in scope”Authentication bypass, credential disclosure, audit redaction failure, audit integrity failure, signing-key handling bugs, source connector data leakage, and privacy regressions that expose raw subject identifiers.
Known pilot limitations, such as no revocation service, no /.well-known/jwt-vc-issuer endpoint,
and no built-in data-subject erasure workflow, are product gaps, not vulnerabilities, unless they
create an exploitable security or privacy issue beyond the documented limitation.