# GHSA-7qf6-h84j-8fq4: OpenClaw: Microsoft Teams media fetch paths bypass shared SSRF guard model

> An SSRF vulnerability in OpenClaw's Microsoft Teams media handling allows attackers to bypass shared security guards and access internal resources.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Mar 2026

## What is GHSA-7qf6-h84j-8fq4?

GHSA-7qf6-h84j-8fq4 is a server-side request forgery vulnerability in openclaw, published on 3 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-7qf6-h84j-8fq4?

2 open source packages ship an affected version, including openclaw.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.2.26 |
| `openclaw` | npm | All versions | 2026.2.26 |

## How do I fix GHSA-7qf6-h84j-8fq4?

Upgrade openclaw to 2026.2.26 or later.

## Is GHSA-7qf6-h84j-8fq4 being exploited?

There is no known exploitation of GHSA-7qf6-h84j-8fq4 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-7qf6-h84j-8fq4 and fix it if it is affected.

What it is: GHSA-7qf6-h84j-8fq4 is a server-side request forgery vulnerability in openclaw, published on 3 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-7qf6-h84j-8fq4 in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.2.26
- openclaw (npm): affected all versions; fixed in 2026.2.26

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-7qf6-h84j-8fq4/ (Markdown: https://insights.sbomify.com/GHSA-7qf6-h84j-8fq4/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-7qf6-h84j-8fq4

---
From sbomify Insights: https://insights.sbomify.com/GHSA-7qf6-h84j-8fq4/
Summaries are generated and may contain mistakes; the official description above is the record.