Every CVESearch/Get API key

GHSA-7qf6-h84j-8fq4

OpenClaw: Microsoft Teams media fetch paths bypass shared SSRF guard model

2.3 LowFix available

GHSA-7qf6-h84j-8fq4 is a low vulnerability (CVSS 2.3) in openclaw, published March 3, 2026. No source lists public exploit code. Fixed in openclaw 2026.2.26.

Severity
2.3 LowCVSS 4.0, GitHub Advisories
Exploit chance
UnscoredNo EPSS score yet
Exploitation
None knownNot on CISA’s or ENISA’s lists
Fixed in
2026.2.26openclaw +1 more

Description

Impact

Microsoft Teams media handling used mixed fetch paths for Graph metadata/content and attachment auth-retry flows. Some paths bypassed the shared SSRF guard model and created inconsistent host/DNS enforcement across redirect/fetch hops.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest published vulnerable version: 2026.2.25
  • Affected range: <= 2026.2.25
  • Planned patched version for next release: 2026.2.26

Technical Details

The Microsoft Teams attachment/media code previously relied on plugin-local fetch behavior in parts of the flow, instead of uniformly using shared guarded fetch logic with pinned DNS + policy checks. This could allow policy drift and SSRF boundary inconsistency between channel/plugin paths.

The fix unifies this path by:

  • routing Microsoft Teams Graph message/hosted-content/attachment fetches through shared SSRF-guarded fetch paths,
  • routing auth-scope fallback attachment downloads through the same guarded policy model,
  • centralizing hostname-suffix allowlist policy helpers in plugin-sdk so channel/plugins use the same allowlist normalization and policy construction behavior.

Fix Commit(s)

  • 57334cd7d85174d5f951de01114fd5801b063564

OpenClaw thanks @tdjackey for reporting.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
High
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
None
Integrity
None
Availability
None

Affected packages

Affected packages
PackageAffectedFixed
openclaw
npm
through 2026.2.25
2026.2.26
openclaw
npm
before 2026.2.26
2026.2.26

What each source reports

GitHub Advisories Score used2.3

OpenClaw: Microsoft Teams media fetch paths bypass shared SSRF guard model

Impact

Microsoft Teams media handling used mixed fetch paths for Graph metadata/content and attachment auth-retry flows. Some paths bypassed the shared SSRF guard model and created inconsistent host/DNS enforcement across redirect/fetch hops.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest published vulnerable version: 2026.2.25
  • Affected range: <= 2026.2.25
  • Planned patched version for next release: 2026.2.26

Technical Details

The Microsoft Teams attachment/media code previously relied on plugin-local fetch behavior in parts of the flow, instead of uniformly using shared guarded fetch logic with pinned DNS + policy checks. This could allow policy drift and SSRF boundary inconsistency between channel/plugin paths.

The fix unifies this path by:

  • routing Microsoft Teams Graph message/hosted-content/attachment fetches through shared SSRF-guarded fetch paths,
  • routing auth-scope fallback attachment downloads through the same guarded policy model,
  • centralizing hostname-suffix allowlist policy helpers in plugin-sdk so channel/plugins use the same allowlist normalization and policy construction behavior.

Fix Commit(s)

  • 57334cd7d85174d5f951de01114fd5801b063564

OpenClaw thanks @tdjackey for reporting.

Record
GHSA-7qf6-h84j-8fq4
CVSS 4.0
2.3 LowCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N
Weakness
CWE-367, CWE-918
Updated
2026-11-02
OSV2.3

OpenClaw: Microsoft Teams media fetch paths bypass shared SSRF guard model

Impact

Microsoft Teams media handling used mixed fetch paths for Graph metadata/content and attachment auth-retry flows. Some paths bypassed the shared SSRF guard model and created inconsistent host/DNS enforcement across redirect/fetch hops.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest published vulnerable version: 2026.2.25
  • Affected range: <= 2026.2.25
  • Planned patched version for next release: 2026.2.26

Technical Details

The Microsoft Teams attachment/media code previously relied on plugin-local fetch behavior in parts of the flow, instead of uniformly using shared guarded fetch logic with pinned DNS + policy checks. This could allow policy drift and SSRF boundary inconsistency between channel/plugin paths.

The fix unifies this path by:

  • routing Microsoft Teams Graph message/hosted-content/attachment fetches through shared SSRF-guarded fetch paths,
  • routing auth-scope fallback attachment downloads through the same guarded policy model,
  • centralizing hostname-suffix allowlist policy helpers in plugin-sdk so channel/plugins use the same allowlist normalization and policy construction behavior.

Fix Commit(s)

  • 57334cd7d85174d5f951de01114fd5801b063564

OpenClaw thanks @tdjackey for reporting.

Record
GHSA-7qf6-h84j-8fq4
CVSS 4.0
2.3 LowCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N
Weakness
CWE-367, CWE-918
Updated
2026-11-02

History

History
RecordedChangedSources
first indexedGitHub Advisories, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

References

PagesAll vulnerabilitiesBrowseDocsSourcesGuideGet API key
MoveEnter Open