CVE-2026-33576 json
OpenClaw < 2026.3.28 - Unauthorized Media Download via Zalo Channel
published 2026-03-31 7 mo ago modified 2026-09-24 45 d ago also GHSA-v2v2-f783-358j , EUVD-2026-17431
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
OpenClaw before 2026.3.28 downloads and stores inbound media from Zalo channels before validating sender authorization. Unauthorized senders can force network fetches and disk writes to the media store by sending messages that are subsequently rejected.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/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 |
| 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.3.28 |
2026.3.28 |
Affected products
- OpenClaw OpenClaw
Classification
References
-
github.com
/openclaw/openclaw/commit/68ceaf7a5f64a23e78b95eff055e4b497218312a
patch, web
-
github.com
/openclaw/openclaw/security/advisories/GHSA-v2v2-f783-358j
vendor-advisory, web
-
vulncheck.com
/advisories/openclaw-unauthorized-media-download-via-zalo-channel
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-33576
advisory
-
github.com
/openclaw/openclaw
package
Sources
- CVE List CVE-2026-33576
- GitHub Advisory GHSA-v2v2-f783-358j
- NVD CVE-2026-33576
Fencer Vulns 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.