Vulnerabilities in pkg:golang/github.com/getaxonflow/axonflow

PACKAGE
Advisory Summary

GHSA-9h64-2846-7x7f is a CRITICAL (CVSS 9.1) axonflow fixed bugs by implementing vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Github.com/getaxonflow/axonflow libraries in the Go ecosystem. The issue involves axonflow fixed bugs by implementing multi-tenant isolation and access-control hardening. Remediation is available by upgrading affected packages to version 7.5.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/getaxonflow/axonflow

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/getaxonflow/axonflow. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-9h64-2846-7x7f - CRITICAL Axonflow fixed bugs by implementing multi-tenant isolation and access-control hardening

GHSA-9h64-2846-7x7f at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-9h64-2846-7x7f
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Affected Product Github.com/getaxonflow/axonflow
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix GHSA-9h64-2846-7x7f

To remediate this vulnerability, upgrade all affected Github.com/getaxonflow/axonflow dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/getaxonflow/axonflow fixed: 7.5.0
Upgrade github.com/getaxonflow/axonflow to 7.5.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/getaxonflow/axonflow

How to Check if You Are Affected

To determine whether your application is affected by GHSA-9h64-2846-7x7f, inspect your project dependencies for Github.com/getaxonflow/axonflow:

inspect dependencies for github.com/getaxonflow/axonflow

Analyze the terminal output to locate any version of Github.com/getaxonflow/axonflow in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.5.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. In Github.com/getaxonflow/axonflow, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary 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 `org_id` 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 `/api/v1/decisions/*/explain` failed open when the tenant context was missing, returning data scoped to a different tenant or returning data without scope. | `< 7.2.0` | `>= 7.2.0` | CWE-200, CWE-863 | | 3 | **License-validation bypass on `onboard-customer`.** The portal customer-onboard endpoint lacked authentication and license-key validation, allowing unauthenticated callers to invoke the onboard flow. | `< 7.2.0` | `>= 7.2.0` | CWE-862 | | 4 | **Tenant-scope fail-open on evidence/explain.** Distinct from item 2: when tenant headers were absent, the handler defaulted to a permissive read scope rather than refusing the request. | `< 7.2.0` | `>= 7.2.0` | CWE-862 | | 5 | **Internal-service auth fallback bypass in non-Community modes.** Evaluation/Enterprise builds carried an auth fallback path that, under specific request shapes, could be exploited to bypass `apiAuthMiddleware`. | `< 7.2.0` | `>= 7.2.0` | CWE-863 | | 6 | **Login timing / org-existence disclosure on the portal.** The login handler returned different timing and response bodies for invalid-org vs invalid-password, allowing org enumeration. | `< 7.1.3` | `>= 7.1.3` | CWE-208 | | 7 | **Portal DoS via unbounded request body.** The portal accepted unbounded request bodies, allowing memory-exhaustion attacks. Capped at 1 MiB. | `< 7.1.5` | `>= 7.1.5` | CWE-770 | | 8 | **SQL-injection enforcement regression on `try.getaxonflow.com`.** The Community SaaS hosted endpoint inherited the `warn` SQLi default introduced in v6.2.0, allowing SQL-injection-shaped requests to pass governance to the LLM. Self-hosted deployments were unaffected unless they manually changed the default. | `< 7.5.0` (try.getaxonflow.com only) | `>= 7.5.0` | CWE-89 | ## Remediation Upgrade to AxonFlow platform **v7.5.0** or later. No configuration changes required — the platform is purely additive and existing API/SDK callers continue to work. For users who can't upgrade immediately, item-specific mitigations: - **Items 1–5:** ensure the agent middleware sets `X-Org-ID` / `X-Tenant-ID` from authenticated identity at the ingress, never accepting body-supplied identity. - **Item 8 (Community SaaS):** `SQLI_ACTION=block` can be set explicitly via the agent task definition; v7.5.0 makes this the default. ## Resources - AxonFlow v7.5.0 CHANGELOG entry: https://github.com/getaxonflow/axonflow/blob/main/CHANGELOG.md - AxonFlow v7.5.0 GitHub Release: https://github.com/getaxonflow/axonflow/releases/tag/v7.5.0 ## Credit Identified by AxonFlow internal security review during the April 2026 quality-freeze epic.

GHSA-9h64-2846-7x7f Affected Github.com/getaxonflow/axonflow Versions

1 component(s)
Fixed Versions:
7.5.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/getaxonflow/axonflow
Go
< 7.5.0
7.5.0

References

Frequently Asked Questions

What is GHSA-9h64-2846-7x7f?
GHSA-9h64-2846-7x7f is a security vulnerability in Github.com/getaxonflow/axonflow involving Axonflow fixed bugs by implementing multi-tenant isolation and access-control hardening under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').
Which Github.com/getaxonflow/axonflow versions are affected?
Affected versions include releases prior to 7.5.0 across affected packages: github.com/getaxonflow/axonflow.
What version fixes GHSA-9h64-2846-7x7f?
Upgrading to 7.5.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/getaxonflow/axonflow affected?
Yes, github.com/getaxonflow/axonflow is affected in releases prior to 7.5.0. Upgrade your dependency to 7.5.0 or later.
What is the CVSS score of GHSA-9h64-2846-7x7f?
GHSA-9h64-2846-7x7f has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L.
What CWE is associated with GHSA-9h64-2846-7x7f?
GHSA-9h64-2846-7x7f is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.).
How can I check Go dependencies for GHSA-9h64-2846-7x7f?
Run the dependency tree command: 'inspect dependencies for github.com/getaxonflow/axonflow'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9h64-2846-7x7f",
  "modified" : "2026-05-06T23:13:27Z",
  "published" : "2026-05-06T23:13:27Z",
  "aliases" : [ ],
  "summary" : "Axonflow fixed bugs by implementing multi-tenant isolation and access-control hardening",
  "details" : "## Summary\n\nEight 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.\n\n## Affected versions\n\n`< 7.5.0`. Specific items affect different earlier minors; see Impact below.\n\n## Patched versions\n\n`>= 7.5.0`.\n\n## Impact\n\n| # | Item | Affected | Patched | CWE |\n|---|---|---|---|---|\n| 1 | **MAP execution multi-tenant isolation.** A body-supplied `org_id` 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 |\n| 2 | **Cross-tenant audit-log leak via evidence/explain handlers.** The handlers behind `/api/v1/evidence/*` and `/api/v1/decisions/*/explain` failed open when the tenant context was missing, returning data scoped to a different tenant or returning data without scope. | `< 7.2.0` | `>= 7.2.0` | CWE-200, CWE-863 |\n| 3 | **License-validation bypass on `onboard-customer`.** The portal customer-onboard endpoint lacked authentication and license-key validation, allowing unauthenticated callers to invoke the onboard flow. | `< 7.2.0` | `>= 7.2.0` | CWE-862 |\n| 4 | **Tenant-scope fail-open on evidence/explain.** Distinct from item 2: when tenant headers were absent, the handler defaulted to a permissive read scope rather than refusing the request. | `< 7.2.0` | `>= 7.2.0` | CWE-862 |\n| 5 | **Internal-service auth fallback bypass in non-Community modes.** Evaluation/Enterprise builds carried an auth fallback path that, under specific request shapes, could be exploited to bypass `apiAuthMiddleware`. | `< 7.2.0` | `>= 7.2.0` | CWE-863 |\n| 6 | **Login timing / org-existence disclosure on the portal.** The login handler returned different timing and response bodies for invalid-org vs invalid-password, allowing org enumeration. | `< 7.1.3` | `>= 7.1.3` | CWE-208 |\n| 7 | **Portal DoS via unbounded request body.** The portal accepted unbounded request bodies, allowing memory-exhaustion attacks. Capped at 1 MiB. | `< 7.1.5` | `>= 7.1.5` | CWE-770 |\n| 8 | **SQL-injection enforcement regression on `try.getaxonflow.com`.** The Community SaaS hosted endpoint inherited the `warn` SQLi default introduced in v6.2.0, allowing SQL-injection-shaped requests to pass governance to the LLM. Self-hosted deployments were unaffected unless they manually changed the default. | `< 7.5.0` (try.getaxonflow.com only) | `>= 7.5.0` | CWE-89 |\n\n## Remediation\n\nUpgrade to AxonFlow platform **v7.5.0** or later. No configuration changes required — the platform is purely additive and existing API/SDK callers continue to work.\n\nFor users who can't upgrade immediately, item-specific mitigations:\n\n- **Items 1–5:** ensure the agent middleware sets `X-Org-ID` / `X-Tenant-ID` from authenticated identity at the ingress, never accepting body-supplied identity.\n- **Item 8 (Community SaaS):** `SQLI_ACTION=block` can be set explicitly via the agent task definition; v7.5.0 makes this the default.\n\n## Resources\n\n- AxonFlow v7.5.0 CHANGELOG entry: https://github.com/getaxonflow/axonflow/blob/main/CHANGELOG.md\n- AxonFlow v7.5.0 GitHub Release: https://github.com/getaxonflow/axonflow/releases/tag/v7.5.0\n\n## Credit\n\nIdentified by AxonFlow internal security review during the April 2026 quality-freeze epic.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/getaxonflow/axonflow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "7.5.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/getaxonflow/axonflow/security/advisories/GHSA-9h64-2846-7x7f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/getaxonflow/axonflow"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getaxonflow/axonflow/blob/main/CHANGELOG.md"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getaxonflow/axonflow/releases/tag/v7.5.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-208", "CWE-770", "CWE-862", "CWE-863", "CWE-89" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-06T23:13:27Z",
    "nvd_published_at" : null
  }
}