GHSA-xwcj-hwhf-h378: Openclaw OpenClaw Telegram Media Fetch Errors Vulnerability

MODERATE
Share
CWE-532
Published
Advisory Summary

GHSA-xwcj-hwhf-h378 is a MODERATE openclaw telegram media fetch errors vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw telegram media fetch errors exposed bot tokens in logged file urls. Remediation is available by upgrading affected packages to version 2026.3.13.

GHSA-xwcj-hwhf-h378 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-xwcj-hwhf-h378
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Openclaw
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-xwcj-hwhf-h378

To remediate this vulnerability, upgrade all affected Openclaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.3.13 
npm install openclaw@2026.3.13
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-xwcj-hwhf-h378, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of Openclaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.3.13), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In Openclaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary `openclaw` versions `<= 2026.3.12` could include raw Telegram bot tokens in media fetch error strings when inbound Telegram media downloads failed. ### Affected Packages / Versions - Package: `openclaw` (`npm`) - Affected versions: `<= 2026.3.12` - Fixed version: `2026.3.13` ### Details The vulnerable path was `fetchRemoteMedia()` in `src/media/fetch.ts`. In affected releases, fetch and HTTP error paths embedded the original Telegram file URL into `MediaFetchError` messages. For Telegram media, those URLs can include `/file/bot<TOKEN>/...`, so the resulting error strings could leak bot tokens into logs, console output, or any downstream error surface that rendered the exception text. This issue is in scope under OpenClaw's trust model because the leaked secret is an OpenClaw-operated integration credential, not a user-supplied third-party secret. ### Fix `openclaw@2026.3.13` redacts sensitive media URLs before constructing fetch error messages. Current code routes the source URL and follow-on error paths through `redactMediaUrl()` / `redactSensitiveText()`, so Telegram bot tokens are no longer emitted in those error strings. Regression coverage exists in `src/media/fetch.test.ts` (`redacts Telegram bot tokens from fetch failure messages` and `redacts Telegram bot tokens from HTTP error messages`). ### Fix Commit(s) - `7a53eb7ea8295b08be137e231c9a98c1a79b5cd5` Thanks @space08 for reporting.

GHSA-xwcj-hwhf-h378 Affected Openclaw Versions

1 component(s)
Fixed Versions:
2026.3.13
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm/openclaw
npm
< 2026.3.13
2026.3.13

References

GitHub Advisory / Wiki ADVISORY
https://github.com/openclaw/openclaw/security/advisories/GHSA-xwcj-hwhf-h378
Security Fix Commit FIX COMMIT
https://github.com/openclaw/openclaw/commit/7a53eb7ea8295b08be137e231c9a98c1a79b5cd5
Openclaw Source Repository REPOSITORY
https://github.com/openclaw/openclaw

Frequently Asked Questions

What is GHSA-xwcj-hwhf-h378?
GHSA-xwcj-hwhf-h378 is a security vulnerability in Openclaw involving OpenClaw Telegram media fetch errors exposed bot tokens in logged file URLs under CWE-532: Insertion of Sensitive Information into Log File.
Which Openclaw versions are affected?
Affected versions include releases prior to 2026.3.13 across affected packages: openclaw.
What version fixes GHSA-xwcj-hwhf-h378?
Upgrading to 2026.3.13 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.3.13. Upgrade your dependency to 2026.3.13 or later.
What CWE is associated with GHSA-xwcj-hwhf-h378?
GHSA-xwcj-hwhf-h378 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check npm dependencies for GHSA-xwcj-hwhf-h378?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xwcj-hwhf-h378",
  "modified" : "2026-03-16T20:40:13Z",
  "published" : "2026-03-16T20:40:13Z",
  "aliases" : [ ],
  "summary" : "OpenClaw Telegram media fetch errors exposed bot tokens in logged file URLs",
  "details" : "### Summary\n`openclaw` versions `<= 2026.3.12` could include raw Telegram bot tokens in media fetch error strings when inbound Telegram media downloads failed.\n\n### Affected Packages / Versions\n- Package: `openclaw` (`npm`)\n- Affected versions: `<= 2026.3.12`\n- Fixed version: `2026.3.13`\n\n### Details\nThe vulnerable path was `fetchRemoteMedia()` in `src/media/fetch.ts`. In affected releases, fetch and HTTP error paths embedded the original Telegram file URL into `MediaFetchError` messages. For Telegram media, those URLs can include `/file/bot<TOKEN>/...`, so the resulting error strings could leak bot tokens into logs, console output, or any downstream error surface that rendered the exception text.\n\nThis issue is in scope under OpenClaw's trust model because the leaked secret is an OpenClaw-operated integration credential, not a user-supplied third-party secret.\n\n### Fix\n`openclaw@2026.3.13` redacts sensitive media URLs before constructing fetch error messages. Current code routes the source URL and follow-on error paths through `redactMediaUrl()` / `redactSensitiveText()`, so Telegram bot tokens are no longer emitted in those error strings.\n\nRegression coverage exists in `src/media/fetch.test.ts` (`redacts Telegram bot tokens from fetch failure messages` and `redacts Telegram bot tokens from HTTP error messages`).\n\n### Fix Commit(s)\n- `7a53eb7ea8295b08be137e231c9a98c1a79b5cd5`\n\nThanks @space08 for reporting.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.3.13"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2026.3.12"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-xwcj-hwhf-h378"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/7a53eb7ea8295b08be137e231c9a98c1a79b5cd5"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-16T20:40:13Z",
    "nvd_published_at" : null
  }
}