# OpenClaw: Telegram legacy allowFrom migration fans default-account trust into all named accounts

Advisory record · `GHSA-f693-58pc-2gfr`

- **Identifiers:** `GHSA-f693-58pc-2gfr` · `CVE-2026-41340`
- **State:** Confirmed
- **Severity:** CVSS 6.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-372](https://cwe.mitre.org/data/definitions/372.html) · [CWE-732](https://cwe.mitre.org/data/definitions/732.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-372](https://agentprime.io/advisories/tag/cwe-372.md)
- **Published:** 3 Apr 2026
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 3 Apr 2026, 03:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `openclaw` (npm): affected `<2026.3.31`; fixed in `2026.3.31`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 3 Apr 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-f693-58pc-2gfr](https://github.com/advisories/GHSA-f693-58pc-2gfr)
- [OSV: GHSA-f693-58pc-2gfr](https://osv.dev/vulnerability/GHSA-f693-58pc-2gfr)
- <https://github.com/openclaw/openclaw/security/advisories/GHSA-f693-58pc-2gfr>
- <https://github.com/openclaw/openclaw/commit/d8c68c8d4265ea6fa5e8c5e056534c351bddef37>
- <https://github.com/openclaw/openclaw>
- <https://github.com/openclaw/openclaw/releases/tag/v2026.3.31>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f693-58pc-2gfr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f693-58pc-2gfr/>. Everything for agents: <https://agentprime.io/llms.txt>.
