Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-57122 – Webhook Signature Bypass Enabling Message Forgery – PraisonAI ≤ 4.6.52

Be the first to know when new zero-days emerge:

Summary

CVE-2026-57122 is a webhook signature verification bypass affecting PraisonAI, an open-source AI agent framework. The WhatsApp and Linear bot adapters skip HMAC signature verification whenever the corresponding webhook secret environment variable is unset — which is the default on a fresh install. This fail-open design lets a remote, unauthenticated attacker send forged webhook events that PraisonAI processes as legitimate, and it carries a CVSS v3.1 score of 8.6 (High).

Technical details

  • Root cause: The WhatsApp and Linear bot adapters guard signature checks with conditionals such as if self._app_secret: and if self._signing_secret:. Because these secrets default to empty strings when not explicitly configured, the entire HMAC verification routine is skipped rather than the request being rejected — a fail-open pattern instead of fail-closed.
  • Trigger conditions: The vulnerable code path is reachable whenever the operator has not explicitly set a webhook signing secret for the WhatsApp or Linear integration — the default state for a fresh install and common in development/test environments.
  • Attack vector: An unauthenticated attacker with network access to the exposed webhook endpoint can send a crafted HTTP POST payload (e.g., mimicking a WhatsApp message) without a valid X-Hub-Signature-256 header. The server accepts the forged request and returns HTTP 200, fully processing it as if it originated from the legitimate messaging platform.
  • Impact: Successful exploitation allows forging inbound bot messages/events, enabling prompt injection into the AI agent, unauthorized command execution within the bot’s context, and impersonation of legitimate users or contacts. The associated CVSS vector reflects low confidentiality impact, high integrity impact, and low availability impact.

Affected software

  • Product: PraisonAI (PyPI package praisonai, vendor MervinPraison)
  • Affected versions: All versions up to and including 4.6.52
  • Fixed version: 4.6.59

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
  • Associated weaknesses: CWE-345 (Insufficient Verification of Data Authenticity), CWE-347 (Improper Verification of Cryptographic Signature)

Mitigation and recommended actions

  • Immediate: Upgrade PraisonAI to version 4.6.59 or later, which enforces signature verification correctly regardless of configuration state.
  • If immediate patching is not possible:
    • Explicitly configure and set strong, unique webhook signing secrets (WHATSAPP_APP_SECRET / Linear signing secret equivalents) for every deployed bot adapter — never leave these unset, even in development.
    • Restrict network access to webhook endpoints using firewall rules, IP allow-listing for the messaging platform’s known egress ranges, or an API gateway/WAF in front of the service.
    • Monitor webhook endpoint logs for requests missing valid signature headers or originating from unexpected source IPs, and treat any such traffic as suspicious.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge