Please report security vulnerabilities privately through GitHub's private vulnerability reporting feature. Do not open a public issue for anything that could be exploited.

For communication outside GitHub, reach the maintainers at security@vaara.io. Use PGP if you prefer end-to-end-encrypted email. The current public key is published at https://github.com/vaaraio/vaara/blob/main/docs/signing-keys.md.

Please include:

• A description of the vulnerability and potential impact
• Steps to reproduce (proof-of-concept if possible)
• The affected versions
• Any suggested mitigations

• Acknowledgement: within 3 business days
• Initial assessment: within 10 business days
• Fix or mitigation timeline: communicated after initial assessment

Coordinated disclosure is welcome. We will credit reporters in release notes unless anonymity is requested.

Only the latest minor release receives security fixes. Older minor lines may receive patches at our discretion for severe issues. Releases are frequent, so treat this table as naming the current line rather than a long-term window.

In scope:

• The vaara Python package and its public APIs
• Audit trail integrity and signed-export verification
• Framework integrations shipped in this repository
• Supply-chain integrity of published PyPI artefacts

Out of scope:

• Third-party frameworks (LangChain, CrewAI, etc.): report those upstream
• Issues in consumer applications that use Vaara
• Vulnerabilities in dependencies already reported upstream

1. Reporter submits via the channels above.
2. Maintainer acknowledges within 3 business days.
3. Maintainer investigates and confirms.
4. Fix developed in a private branch.
5. CVE requested where warranted.
6. Patch released and advisory published.
7. Reporter credited in release notes and GitHub Security Advisory.

• Always pin vaara to a specific version in production.
• Verify PyPI artefacts against published checksums and the Sigstore attestations, which ship with every release and are produced by the release workflow alongside SLSA provenance.
• When deploying signed audit exports, protect the signing private key using OS-level key management (hardware-backed keystore or HSM recommended).

The parsers that ingest attacker-controlled bytes (the OVERT envelope CBOR decoder, the audit-record from_dict deserialiser, and the policy YAML/JSON loader) are covered by ClusterFuzzLite under both AddressSanitizer and UndefinedBehaviorSanitizer. PRs that touch src/, fuzz/, .clusterfuzzlite/, or the CFLite workflows trigger short fuzz runs as a status check; a nightly cron runs a longer batch. Fuzz target sources live in fuzz/fuzz_*.py. Reports for crashes found by fuzzing should follow the same private-disclosure path as any other vulnerability.

• OWASP Top 10: https://owasp.org/www-project-top-ten/
• EU AI Act Article 15 (accuracy, robustness, cybersecurity) informs the threat model for runtime governance components.