Summary
OpenClaw: Telegram legacy allowFrom migration fans default-account trust into all named accounts
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.
Impact
A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-F693-58PC-2GFR? GHSA-F693-58PC-2GFR is a medium-severity incorrect permission assignment for critical resource vulnerability in openclaw (npm), affecting versions <= 2026.3.28. It is fixed in 2026.3.31. A file, directory, or other resource is assigned permissions that allow broader access than intended.
- Which versions of openclaw are affected by GHSA-F693-58PC-2GFR? openclaw (npm) versions <= 2026.3.28 is affected.
- Is there a fix for GHSA-F693-58PC-2GFR? Yes. GHSA-F693-58PC-2GFR is fixed in 2026.3.31. Upgrade to this version or later.
- Is GHSA-F693-58PC-2GFR exploitable, and should I be worried? Whether GHSA-F693-58PC-2GFR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-F693-58PC-2GFR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-F693-58PC-2GFR? Upgrade
openclawto 2026.3.31 or later.