What is the CVSS score of CVE-2026-25474?

CVE-2026-25474 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of AI / ML are affected by CVE-2026-25474?

OpenClaw AI assistant versions 2026.1.30 and earlier lack proper authentication for Telegram webhook requests when the secret token is not configured, allowing unauthenticated users to submit…. A patch is available.

Is there a public PoC exploit available for CVE-2026-25474?

Yes, a public proof-of-concept exploit is available for CVE-2026-25474. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-25474?

Within 24 hours: Verify if OpenClaw is deployed in your environment and check if Telegram webhook mode is enabled with channels.telegram.webhookSecret configured. Within 7 days: Apply the available patch to all affected OpenClaw instances and validate that webhookSecret is properly set. Within 30 days: Conduct a log review for any suspicious Telegram webhook requests during the vulnerability window and update your deployment standards to require webhookSecret configuration.

AI / ML CVE-2026-25474

HIGH

Insufficient Verification of Data Authenticity (CWE-345)

2026-02-19 security-advisories@github.com

GHSA-mp5h-m6qj-6292

Authentication Bypass AI / ML Openclaw

7.5

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 22:03 vuln.today

PoC Detected

Feb 19, 2026 - 20:13 vuln.today

Public exploit code

Patch released

Feb 19, 2026 - 20:13 nvd

Patch available

CVE Published

Feb 19, 2026 - 07:17 nvd

HIGH 7.5

DescriptionGitHub Advisory

OpenClaw is a personal AI assistant. In versions 2026.1.30 and below, if channels.telegram.webhookSecret is not set when in Telegram webhook mode, OpenClaw may accept webhook HTTP requests without verifying Telegram’s secret token header. In deployments where the webhook endpoint is reachable by an attacker, this can allow forged Telegram updates (for example spoofing message.from.id). If an attacker can reach the webhook endpoint, they may be able to send forged updates that are processed as if they came from Telegram. Depending on enabled commands/tools and configuration, this could lead to unintended bot actions. Note: Telegram webhook mode is not enabled by default. It is enabled only when channels.telegram.webhookUrl is configured. This issue has been fixed in version 2026.2.1.

AnalysisAI

OpenClaw versions 2026.1.30 and below fail to validate Telegram webhook secret tokens when channels.telegram.webhookSecret is not configured, allowing attackers with network access to the webhook endpoint to forge Telegram messages and trigger unintended bot actions. Public exploit code exists for this vulnerability. Affected deployments must upgrade to version 2026.2.1 or later, or ensure the webhook endpoint is not reachable by untrusted networks.

Technical ContextAI

Classified as CWE-345 (Insufficient Verification of Data Authenticity). Affects the deployments where the webhook component of Openclaw. OpenClaw is a personal AI assistant. In versions 2026.1.30 and below, if channels.telegram.webhookSecret is not set when in Telegram webhook mode, OpenClaw may accept webhook HTTP requests without verifying Telegram’s secret token header. In deployments where the webhook endpoint is reachable by an attacker, this can allow forged Telegram updates (for example spoofing message.from.id). If an attacker can reach the webhook endpoint, they may be able to send forged updates that are processed as if