OpenClaw: Telegram legacy allowFrom migration fans default-account trust into all named accounts
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
## Summary Telegram legacy allowFrom migration fans default-account trust into all named accounts ## Current Maintainer Triage - Status: open - Normalized severity: low - Assessment: Shipped v2026.3.28 Telegram migration fans legacy default-account allowFrom trust into named accounts, which is an in-scope auth-boundary bug and low fits. ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version: `2026.3.31` - Vulnerable version range: `<=2026.3.28` - Patched versions: `>= 2026.3.31` - First stable tag containing the fix: `v2026.3.31` ## Fix Commit(s) - `d8c68c8d4265ea6fa5e8c5e056534c351bddef37` — 2026-03-31T12:51:38+01:00 ## Release Process Note - The fix is already present in released version `2026.3.31`. - This draft looks ready for final maintainer disposition or publication, not additional code-fix work. Thanks @smaeljaish771 for reporting.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | openclaw (npm) | before 2026.3.31 | 2026.3.31 | Patch available | GHSA-f693-58pc-2gfr |
- openclaw (npm) Vendor— Affected before 2026.3.31 Fixed in 2026.3.31 Patch available GHSA-f693-58pc-2gfr
Remediation
- Fix · GHSA-f693-58pc-2gfr openclaw (npm) Fixed in 2026.3.31 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-f693-58pc-2gfr
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences