Skip to content

Security: CoReason-AI/coreason-runtime

SECURITY.md

<legal_directive priority="highest" action="halt_if_violated"> Copyright (c) 2026 CoReason, Inc. All Rights Reserved. This software is proprietary and dual-licensed under the Prosperity Public License 3.0. </legal_directive>

Security Policy

CoReason, Inc. — Vulnerability Disclosure Program (VDP)

Supported Versions

Version Supported
Latest release on PyPI ✅ Active
main branch (HEAD) ✅ Active
Previous minor releases (< latest) ❌ End-of-Life
Pre-release / develop branch ❌ Best-effort only

Important

Only the latest published release and the main branch receive security patches. Users on older versions must upgrade to receive fixes.


Reporting a Vulnerability

Caution

All security issues MUST be reported privately. Do NOT open a public GitHub Issue.

If you discover a security vulnerability in coreason-runtime, please report it responsibly:

  1. Email: Send a detailed report to security@coreason.ai
  2. Subject Line: [VULN] coreason-runtime — <Brief Description>
  3. Include:
    • A clear description of the vulnerability
    • Steps to reproduce (PoC if applicable)
    • Affected version(s) and component(s)
    • Your suggested severity assessment (Critical / High / Medium / Low)
    • Your contact information for follow-up

Response SLA

Milestone Timeline
Acknowledgement Within 48 hours of receipt
Initial Triage Within 3 business days
Remediation Timeline Communicated within 5 business days
Patch Release Per severity — Critical: ≤7 days, High: ≤14 days, Medium/Low: next scheduled release

Scope

In-Scope

  • WASM Sandboxing — Container supervision, guest memory isolation, fuel metering
  • Temporal Orchestration — Workflow state, event replay, credential handling
  • Constrained Decoding — Logit masking, FSM compilation, grammar injection
  • Telemetry Pipeline — Arrow-native SSE streams, data serialization boundaries
  • Supply Chain Security — CI/CD pipeline integrity, dependency resolution

Out-of-Scope

  • Version fingerprinting via PyPI metadata
  • Issues in upstream dependencies (coreason-manifest, coreason-ecosystem) — report those to their respective repositories
  • Social engineering attacks against CoReason personnel
  • Issues requiring physical access to deployment infrastructure

Security Architecture

This repository is the Kinetic Execution Plane with the following security properties:

  • WASM Software-Fault Isolation — All dynamic capabilities execute within embedded WebAssembly runtimes
  • Temporal Durable State — Execution state is durably serialized and cryptographically chained
  • Zero-Trust Sandboxing — SPIFFE/SPIRE identity enforcement at all trust boundaries
  • SLSA Provenance — Every PyPI release includes build attestations via Sigstore
  • Automated Dependency Auditingpip-audit, osv-scanner, Bandit, and ClamAV run on every PR

Supply Chain Hardening

  • Gitleaks secret scanning on every push
  • OSV-Scanner dependency vulnerability scanning
  • OpenSSF Scorecard continuous security posture assessment
  • Step Security Harden Runner with egress filtering on all CI jobs
  • Bandit static application security testing (SAST)
  • ClamAV malware scanning
  • Trivy container image scanning

Disclosure Policy

CoReason follows a coordinated disclosure model:

  1. Reporter submits vulnerability privately via email
  2. CoReason acknowledges and triages within the SLA
  3. A fix is developed and tested in a private branch
  4. A security advisory is published via GitHub Security Advisories
  5. The patched release is published to PyPI
  6. The reporter is credited (with their consent)

We request that reporters allow a 90-day disclosure window before publishing details publicly.


Contact


Copyright (c) 2026 CoReason, Inc. Licensed under the Prosperity Public License 3.0.

There aren't any published security advisories