CVE-2026-28454 json
OpenClaw < 2026.2.2 - Authorization Bypass via Unauthenticated Telegram Webhook
published 8mo ago modified 4mo ago also GHSA-fhvm-j76f-qmjv , EUVD-2026-9903
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
OpenClaw versions prior to 2026.2.2 fail to validate webhook secrets in Telegram webhook mode (must be enabled), allowing unauthenticated HTTP POST requests to the webhook endpoint that trust attacker-controlled JSON payloads. Remote attackers can forge Telegram updates by spoofing message.from.id and chat.id fields to bypass sender allowlists and execute privileged bot commands.
Patch / fix
- npm openclaw 2026.2.1
- OpenClaw OpenClaw 2026.2.2
Is CVE-2026-28454 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/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 |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | openclaw | <2026.2.1 |
2026.2.1 |
Affected products
- OpenClaw OpenClaw
Classification
References
-
github.com
/openclaw/openclaw/commit/ca92597e1f9593236ad86810b66633144b69314d
patch, web
-
github.com
/openclaw/openclaw/commit/5643a934799dc523ec2ef18c007e1aa2c386b670
patch, web
-
github.com
/openclaw/openclaw/commit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930
patch, web
-
github.com
/openclaw/openclaw/commit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09
patch, web
-
github.com
/openclaw/openclaw/security/advisories/GHSA-fhvm-j76f-qmjv
vendor-advisory, web, mitigation
-
vulncheck.com
/advisories/openclaw-authorization-bypass-via-unauthenticated-telegram-webhook
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-28454
advisory
-
github.com
/openclaw/openclaw
package
-
github.com
/openclaw/openclaw/releases/tag/v2026.2.1
web
Sources
- CVE List CVE-2026-28454
- GitHub Advisory GHSA-fhvm-j76f-qmjv
- NVD CVE-2026-28454
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.