Skip to content

← Public intelligence

Go package

github.com/getaxonflow/axonflow

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.1GoPublished

    Axonflow fixed bugs by implementing multi-tenant isolation and access-control hardening

    GHSA-9h64-2846-7x7f

    Affected
    • Go github.com/getaxonflow/axonflow < 7.5.0
    Fixed in
    7.5.0· Vendor fix available
    Issue
    Eight independently-filed bug fixes in the v7.1.3 → v7.5.0 release window collectively close a set of multi-tenant isolation, access-control, and policy-enforcement defects in the AxonFlow platform. They are filed as a single consolidated advisory because the recommended remediation is a single platform upgrade. Affected versions < 7.5.0. Specific items affect different earlier minors; see Impact below. Patched versions = 7.5.0. Impact | | Item | Affected | Patched | CWE | |---|---|---|---|---| | 1 | MAP execution multi-tenant isolation. A body-supplied orgid could override the Basic-auth-derived org for both execution recording and policy evaluation. In multi-tenant deployments with shared agents, this could record one tenant's request under another tenant's audit log and evaluate it under the wrong tenant's policy set. | < 7.4.5 | = 7.4.5 | CWE-863 | | 2 | Cross-tenant audit-log leak via evidence/explain handlers. The handlers behind /api/v1/evidence/ and…

    Recommended action: Upgrade to 7.5.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →