GHSA-7f4h-6264-89fr axonflow-sdk-python: Webhook signing-key (HMAC-SHA256) not exposed by SDK type, preventing signature verification
Developers using the AxonFlow Python SDK cannot verify webhook signatures, allowing attackers to forge events if the webhook URL is known.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-7f4h-6264-89fr?
GHSA-7f4h-6264-89fr is a vulnerability in axonflow, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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:
- Skip signature verification entirely — accepting any payload from any source that knew the webhook URL.
- 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 6.6.2 and below.
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:
- Persist the secret returned by
CreateWebhooksecurely (it is only returned once, at create time). - On each incoming webhook delivery, compute
HMAC-SHA256(secret, raw_body)and compare it in constant time against theX-AxonFlow-Signatureheader. - Reject any delivery whose signature does not match.
Credit
Identified by AxonFlow internal security review during the April 2026 quality-freeze epic.
Which versions are affected by GHSA-7f4h-6264-89fr?
2 open source packages ship an affected version, including axonflow.
| Package | Affected | Fixed in |
|---|---|---|
axonflow PyPI | All versions | 6.7.0 |
axonflow PyPI | All versions | 6.7.0 |
How do I fix GHSA-7f4h-6264-89fr?
Upgrade axonflow to 6.7.0 or later.
Is GHSA-7f4h-6264-89fr being exploited?
There is no known exploitation of GHSA-7f4h-6264-89fr in the wild and no public exploit code.