Skip to content
CriticalVulnerabilityLLM-specific

GHSA-9h64-2846-7x7f: Axonflow fixed bugs by implementing multi-tenant isolation and access-control hardening

Published
Record updated
View JSON
Affected
  • github.com/getaxonflow/axonflow < 7.5.0
Fixed in
7.5.0

Summary

AxonFlow's GHSA-9h64-2846-7x7f advisory consolidates eight bug fixes in the v7.1.3 to v7.5.0 window, closing multi-tenant isolation, access-control and policy-enforcement defects. Affected versions are below 7.5.0, with individual items affecting different earlier minors. A body-supplied org_id could override the authenticated org, letting one tenant's requests be recorded in another tenant's audit log and evaluated under the wrong policy set.

Mitigation

Upgrade to AxonFlow platform v7.5.0 or later. No configuration changes are required. For users who cannot upgrade immediately, the source gives item-specific mitigations: for items 1-5, ensure the agent middleware sets X-Org-ID / X-Tenant-ID from authenticated identity at the ingress and never accepts body-supplied identity; for item 8 (Community SaaS), set SQLI_ACTION=block explicitly via the agent task definition, which v7.5.0 makes the default.