Do not open a public GitHub issue for security vulnerabilities.

Email: security@aevum.build

Response within 72 hours. Confirmed vulnerabilities addressed in a patch release. Credit given in release notes unless you prefer anonymity.

Aevum's key security properties:

• SHA-256 Merkle chain audit trail — tamper-evident, cannot be silently altered
• Ed25519-signed principles verified at boot (runtime verification in Phase 1)
• Five absolute barriers enforced via Cedar forbid policies (non-bypassable)
• Append-only audit trail enforced at storage layer (no UPDATE or DELETE)
• Consent gate verified before every context traversal
• Crisis detection runs before any graph write

Full threat model: THREAT_MODEL.md

• pip-audit on every CI push
• OpenSSF Scorecard badge — Phase 9
• CycloneDX SBOM on every release — Phase 9
• PyPI Trusted Publishing (OIDC, no stored API keys) — Phase 9

Aevum's security model depends on where the signing key lives relative to the agent's trust boundary.

For regulated deployments (FDA 21 CFR §11.10(e), EU AI Act Article 12, HIPAA §164.312(b) requiring independently-recorded audit trails): use an external signer. The signing key must live outside the agent's trust boundary.

See ADR-004 for the full trust-boundary analysis.

The five barriers cannot be disabled by any policy, configuration, or complication:

1. Crisis detection — halts processing on crisis content
2. Classification ceiling — enforces data classification limits
3. Consent enforcement — requires valid consent for all operations
4. Audit immutability — prevents audit log modification
5. Provenance — records data lineage

Trademark search for "Aevum": TESS (USPTO) Class 9 and 42, and EUIPO equivalent, is required before the first public PyPI release under the aevum-core name. Status: pending maintainer action. No filing has been made. This is a manual step — the maintainer must initiate the search and record the outcome here before the 1.0.0 release.

Original filing: FILED — 2026-05-20 Supplemental filing (ML-DSA-65): FILED — 2026-05-24

Original filing: 2026-05-20. Sent to crypt@bis.doc.gov and enc@nsa.gov. Supplemental filing: 2026-05-24. Additional algorithm notified: ML-DSA-65 (FIPS 204, Module-Lattice-Based Digital Signature Algorithm — post-quantum digital signatures). No response required — notification only.

All algorithms are published, standardized algorithms. No proprietary cryptographic functionality is implemented. Contact: security@aevum.build

Aevum-core uses Ed25519 digital signatures, ML-DSA-65 post-quantum signatures, and SHA3-256 hashing. These are encryption items subject to EAR (Export Administration Regulations) §742.15. Open-source cryptographic software qualifies for the License Exception ENC (15 C.F.R. §740.17(b)(4)) — a one-time notification to BIS and NSA is sufficient; no license is required.

Per 15 C.F.R. §742.15(b) and §740.17(b)(4):

1. Submit the notification by email to: crypt@bis.doc.gov and enc@nsa.gov
2. The subject line must read: "NOTIFICATION OF INTERNET DOWNLOAD SITE FOR ENCRYPTION SOURCE CODE OR OBJECT CODE"
3. Submit once, before or at the time of public release.
4. Retain a copy of the submission confirmation.

To: crypt@bis.doc.gov, enc@nsa.gov
Subject: NOTIFICATION OF INTERNET DOWNLOAD SITE FOR ENCRYPTION SOURCE CODE
         OR OBJECT CODE

In accordance with 15 C.F.R. §742.15(b) and §740.17(b)(4), Aevum Labs
hereby notifies BIS and NSA of the availability of open-source encryption
software at the following URL:

  https://github.com/aevum-labs/aevum

Product name: aevum-core
Version: 0.6.0 (and all subsequent versions)
Maintainer: Aevum Labs
Contact email: security@aevum.build

Description of encryption functionality:
  aevum-core uses the following cryptographic algorithms for audit chain
  integrity and digital signing:
  - Ed25519 digital signatures (RFC 8032) for AuditEvent signing
  - SHA3-256 (FIPS 202) for hash chaining and payload integrity
  - SHA-256 (FIPS 180-4) for Rekor transparency log submission

  These algorithms are used exclusively for:
  - Authentication of audit records (signing, not encryption of payload)
  - Data integrity verification (hash chains)
  - External transparency log anchoring

  aevum-core does NOT implement its own cryptographic algorithms. It uses
  the following open-source libraries:
  - cryptography (pyca/cryptography) — Apache-2.0, uses OpenSSL under the hood
  - hashlib (Python standard library) — uses system OpenSSL or libtomcrypt

License: Apache-2.0
Source code URL: https://github.com/aevum-labs/aevum
PyPI: https://pypi.org/project/aevum-core/

This software is publicly available at no charge. It is not subject to
EAR99 because it performs encryption; however, it qualifies for License
Exception ENC under 15 C.F.R. §740.17(b)(4) as publicly available
encryption source code.

Date filed: 2026-05-20