Tessera is identity- and cryptography-adjacent infrastructure, so security reports are taken seriously. Thank you for helping keep it and its users safe.

Fixes land on the latest release line. Packages are published on nuget.org under the Sagynbaev.Tessera* prefix via Trusted Publishing (OIDC) — no long-lived API key is stored.

Please do not open a public issue for a security vulnerability.

Report it privately via GitHub's Private vulnerability reporting (repo → Security → Report a vulnerability). If that is unavailable, contact the maintainer @asagynbaev and ask for a private channel before sharing details.

When reporting, please include:

• affected package(s) and version(s) (e.g. Sagynbaev.Tessera.Cryptography 3.3.0);
• a description of the issue and its impact;
• a minimal reproduction or proof of concept, if possible.

You can expect an initial acknowledgement within a few days. Coordinated disclosure is preferred: we will work with you on a fix and a release before any public write-up.

The cryptographic core (Tessera.Cryptography: from-scratch secp256k1, Pedersen commitments, and Bulletproofs) is not constant-time and has not had an external cryptographic audit. In particular, Point.ScalarMul is a branch-on-bit double-and-add (leaks the scalar to timing/SPA), and the claim-canonicalization wire format is length-prefixed but not type-tagged. Do not use it to protect funds or high-value secrets until that audit is complete.

The full threat model, what is in/out of scope, the deterministic test vectors, and the deferred items are documented in docs/security-audit-readiness.md — the dossier an external auditor should start from. On-chain contract notes (e.g. the EVM registerDid controller-signature ABI change in v3.2.0) are tracked there and in the per-chain READMEs.