GHSA-248h-974q-xrc2: axonflow-sdk-java Webhook Signing-key (HMAC-SHA256) Not Exposed Vulnerability

MODERATE
CVSS 5.9
CWE-345 CWE-347
Published
Advisory Summary

GHSA-248h-974q-xrc2 is a MODERATE (CVSS 5.9) webhook signing-key (hmac-sha256) not exposed vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting axonflow-sdk-java libraries in the Maven ecosystem. The issue involves webhook signing-key (hmac-sha256) not exposed by sdk type, preventing signature verification. Remediation is available by upgrading affected packages to version 7.0.0.

GHSA-248h-974q-xrc2 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-248h-974q-xrc2
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product axonflow-sdk-java
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.9

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

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

How to Fix GHSA-248h-974q-xrc2

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

com.getaxonflow:axonflow-sdk fixed: 7.0.0
<dependency>
    <groupId>com.getaxonflow</groupId>
    <artifactId>axonflow-sdk</artifactId>
    <version>7.0.0</version>
</dependency>
Verify Direct and Transitive Dependencies

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

mvn dependency:tree -Dincludes=com.getaxonflow

How to Check if You Are Affected

To determine whether your Java application is affected by GHSA-248h-974q-xrc2, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=com.getaxonflow

Analyze the terminal output to locate any version of axonflow-sdk-java in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.0.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=com.getaxonflow command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In axonflow-sdk-java, 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 The AxonFlow SDK's `WebhookSubscription` (or equivalent) type did not expose the HMAC-SHA256 signing key returned by the platform's `CreateWebhook` endpoint. Without access to the secret through the typed SDK API, callers had no path to verify the `X-AxonFlow-Signature` header on incoming webhook deliveries. Affected callers had two unsatisfactory options: 1. Skip signature verification entirely — accepting any payload from any source that knew the webhook URL. 2. Hand-parse the raw HTTP JSON response to extract the secret, bypassing the type-safe SDK surface. This advisory is filed across all four AxonFlow SDKs (Go, Python, TypeScript, Java) because the same defect and the same fix landed in each. ## Affected versions Versions prior to 7.0.0. ## Impact A webhook receiver using the SDK's typed API to handle inbound deliveries had no path to authenticate the source of incoming payloads. An attacker who learned the webhook URL — through misconfiguration, log leakage, observable network traffic during setup, or any other discovery channel — could forge webhook deliveries indistinguishable from legitimate ones, causing the receiving application to act on fabricated events (e.g. simulated approval-granted callbacks, simulated policy-decision callbacks, simulated step-completion callbacks). ## Remediation Upgrade to the patched version listed in Vulnerabilities below. The signing key is now exposed on the `WebhookSubscription` response type returned by `CreateWebhook`. Implementations should: 1. Persist the secret returned by `CreateWebhook` securely (it is only returned once, at create time). 2. On each incoming webhook delivery, compute `HMAC-SHA256(secret, raw_body)` and compare it in constant time against the `X-AxonFlow-Signature` header. 3. Reject any delivery whose signature does not match. ## Credit Identified by AxonFlow internal security review during the April 2026 quality-freeze epic.

GHSA-248h-974q-xrc2 Affected axonflow-sdk-java Versions

1 component(s)
Fixed Versions:
7.0.0
Product / Package Ecosystem Affected Versions Fixed Version
com.getaxonflow:axonflow-sdk
Maven
< 7.0.0
7.0.0

References

Frequently Asked Questions

What is GHSA-248h-974q-xrc2?
GHSA-248h-974q-xrc2 is a security vulnerability in axonflow-sdk-java involving Webhook signing-key (HMAC-SHA256) not exposed by SDK type, preventing signature verification under CWE-345: Insufficient Verification of Data Authenticity.
Which axonflow-sdk-java versions are affected?
Affected versions include releases prior to 7.0.0 across affected packages: com.getaxonflow:axonflow-sdk.
What version fixes GHSA-248h-974q-xrc2?
Upgrading to 7.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is axonflow-sdk affected?
Yes, com.getaxonflow:axonflow-sdk is affected in releases prior to 7.0.0. Upgrade your dependency to 7.0.0 or later.
What is the CVSS score of GHSA-248h-974q-xrc2?
GHSA-248h-974q-xrc2 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with GHSA-248h-974q-xrc2?
GHSA-248h-974q-xrc2 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Maven dependencies for GHSA-248h-974q-xrc2?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=com.getaxonflow'. 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-248h-974q-xrc2",
  "modified" : "2026-09-02T16:03:23Z",
  "published" : "2026-05-06T23:16:58Z",
  "aliases" : [ ],
  "summary" : "axonflow-sdk-java: Webhook signing-key (HMAC-SHA256) not exposed by SDK type, preventing signature verification",
  "details" : "## Summary\n\nThe AxonFlow SDK's `WebhookSubscription` (or equivalent) type did not expose the HMAC-SHA256 signing key returned by the platform's `CreateWebhook` endpoint. Without access to the secret through the typed SDK API, callers had no path to verify the `X-AxonFlow-Signature` header on incoming webhook deliveries. Affected callers had two unsatisfactory options:\n\n1. Skip signature verification entirely — accepting any payload from any source that knew the webhook URL.\n2. Hand-parse the raw HTTP JSON response to extract the secret, bypassing the type-safe SDK surface.\n\nThis advisory is filed across all four AxonFlow SDKs (Go, Python, TypeScript, Java) because the same defect and the same fix landed in each.\n\n## Affected versions\n\nVersions prior to 7.0.0.\n\n## Impact\n\nA webhook receiver using the SDK's typed API to handle inbound deliveries had no path to authenticate the source of incoming payloads. An attacker who learned the webhook URL — through misconfiguration, log leakage, observable network traffic during setup, or any other discovery channel — could forge webhook deliveries indistinguishable from legitimate ones, causing the receiving application to act on fabricated events (e.g. simulated approval-granted callbacks, simulated policy-decision callbacks, simulated step-completion callbacks).\n\n## Remediation\n\nUpgrade to the patched version listed in Vulnerabilities below. The signing key is now exposed on the `WebhookSubscription` response type returned by `CreateWebhook`. Implementations should:\n\n1. Persist the secret returned by `CreateWebhook` securely (it is only returned once, at create time).\n2. On each incoming webhook delivery, compute `HMAC-SHA256(secret, raw_body)` and compare it in constant time against the `X-AxonFlow-Signature` header.\n3. Reject any delivery whose signature does not match.\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:H/PR:N/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "com.getaxonflow:axonflow-sdk"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "7.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/getaxonflow/axonflow-sdk-java/security/advisories/GHSA-248h-974q-xrc2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getaxonflow/axonflow-sdk-java/pull/156"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getaxonflow/axonflow-sdk-java/commit/53c049a2ff34e7d9ef428bf6f24dac050200f5bc"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/getaxonflow/axonflow-sdk-java"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/getaxonflow/axonflow-sdk-java/blob/bac65ce6143327e1f9201d0dc73815e93dcdb47c/CHANGELOG.md?plain=1#L632"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345", "CWE-347" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-06T23:16:58Z",
    "nvd_published_at" : null
  }
}