GHSA-j26j-7qc4-3mrf: OpenClaw MS Teams FileConsent/invoke Missing Conversation Vulnerability

MODERATE
Share
CWE-639 CWE-862
Published
Advisory Summary

GHSA-j26j-7qc4-3mrf is a MODERATE ms teams fileconsent/invoke missing conversation vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting OpenClaw libraries in the npm ecosystem. The issue involves ms teams fileconsent/invoke missing conversation binding allowed cross-conversation pending-upload consumption. Remediation is available by upgrading affected packages to version 2026.2.25.

GHSA-j26j-7qc4-3mrf at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-j26j-7qc4-3mrf
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product OpenClaw
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-j26j-7qc4-3mrf

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.2.25 
npm install openclaw@2026.2.25
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-j26j-7qc4-3mrf, 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.2.25), 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-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. 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 In `openclaw` MS Teams file-consent flow, pending uploads were authorized by `uploadId` alone. `fileConsent/invoke` did not verify the invoke conversation against the conversation that created the pending upload. ### Impact An attacker who obtained a valid `uploadId` within TTL could trigger cross-conversation upload completion (accept path) or cancel a victim pending upload (decline path). ### Technical Details - Pending uploads stored `conversationId`, but invoke handling consumed by `uploadId` only. - The invoke path did not enforce conversation binding before `uploadToConsentUrl(...)` and pending-upload removal. - Fix binds accept/decline handling to normalized conversation id match before consuming pending upload state. ### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version (as of February 26, 2026): `2026.2.24` - Vulnerable range: `<= 2026.2.24` - Patched in release: `2026.2.25` ### Remediation Upgrade to `openclaw` `2026.2.25` (or later) once published. ### Fix Commit(s) - `347f7b9550064f5f5b33c6e07f64e85b9657b6f1` ### Release Process Note `patched_versions` is pre-set to the release (`2026.2.25`). Advisory published with npm release `2026.2.25`. OpenClaw thanks @tdjackey for reporting.

GHSA-j26j-7qc4-3mrf Affected OpenClaw Versions

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

References

GitHub Advisory / Wiki ADVISORY
https://github.com/openclaw/openclaw/security/advisories/GHSA-j26j-7qc4-3mrf
Security Fix Commit FIX COMMIT
https://github.com/openclaw/openclaw/commit/347f7b9550064f5f5b33c6e07f64e85b9657b6f1
OpenClaw Source Repository REPOSITORY
https://github.com/openclaw/openclaw

Frequently Asked Questions

What is GHSA-j26j-7qc4-3mrf?
GHSA-j26j-7qc4-3mrf is a security vulnerability in OpenClaw involving MS Teams fileConsent/invoke missing conversation binding allowed cross-conversation pending-upload consumption under CWE-639: Authorization Bypass Through User-Controlled Key.
Which OpenClaw versions are affected?
Affected versions include releases prior to 2026.2.25 across affected packages: openclaw.
What version fixes GHSA-j26j-7qc4-3mrf?
Upgrading to 2026.2.25 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.2.25. Upgrade your dependency to 2026.2.25 or later.
What CWE is associated with GHSA-j26j-7qc4-3mrf?
GHSA-j26j-7qc4-3mrf is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check npm dependencies for GHSA-j26j-7qc4-3mrf?
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-j26j-7qc4-3mrf",
  "modified" : "2026-03-03T21:36:49Z",
  "published" : "2026-03-03T21:36:49Z",
  "aliases" : [ ],
  "summary" : "OpenClaw: MS Teams fileConsent/invoke missing conversation binding allowed cross-conversation pending-upload consumption",
  "details" : "### Summary\nIn `openclaw` MS Teams file-consent flow, pending uploads were authorized by `uploadId` alone. `fileConsent/invoke` did not verify the invoke conversation against the conversation that created the pending upload.\n\n### Impact\nAn attacker who obtained a valid `uploadId` within TTL could trigger cross-conversation upload completion (accept path) or cancel a victim pending upload (decline path).\n\n### Technical Details\n- Pending uploads stored `conversationId`, but invoke handling consumed by `uploadId` only.\n- The invoke path did not enforce conversation binding before `uploadToConsentUrl(...)` and pending-upload removal.\n- Fix binds accept/decline handling to normalized conversation id match before consuming pending upload state.\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Latest published npm version (as of February 26, 2026): `2026.2.24`\n- Vulnerable range: `<= 2026.2.24`\n- Patched in release: `2026.2.25`\n\n### Remediation\nUpgrade to `openclaw` `2026.2.25` (or later) once published.\n\n### Fix Commit(s)\n- `347f7b9550064f5f5b33c6e07f64e85b9657b6f1`\n\n### Release Process Note\n`patched_versions` is pre-set to the release (`2026.2.25`). Advisory published with npm release `2026.2.25`.\n\nOpenClaw thanks @tdjackey for reporting.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.2.25"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2026.2.24"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-j26j-7qc4-3mrf"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/347f7b9550064f5f5b33c6e07f64e85b9657b6f1"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639", "CWE-862" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-03T21:36:49Z",
    "nvd_published_at" : null
  }
}