# CVE-2026-100526: Vulnerability in discord

> An attacker with guild asset access can bypass media policy restrictions to read arbitrary local files via emoji or sticker upload actions.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-hfjp-hq7w-7gcf, GHSA-xvwp-wmh2-fq48

## What is CVE-2026-100526?

CVE-2026-100526 is a medium-severity path traversal vulnerability in openclaw discord, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw's Discord integration (npm package @openclaw/discord) before version 2026.9.3 could lose the sender-scoped media policy in the emoji and sticker upload actions before loading a local file. A sender permitted to invoke those actions could cause OpenClaw to read a host path that the same sender's configured media roots would otherwise reject, placing bytes from an out-of-policy local file into an outbound emoji or sticker upload. Exploitation requires access to the guild asset action and knowledge or derivation of a useful local path; the issue does not permit unrestricted filesystem browsing or code execution. The issue is fixed in @openclaw/discord 2026.9.3.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-100526?


## How do I fix CVE-2026-100526?

No fix has been published for CVE-2026-100526 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100526 being exploited?

There is no known exploitation of CVE-2026-100526 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100526 and fix it if it is affected.

What it is: CVE-2026-100526 is a medium-severity path traversal vulnerability in openclaw discord, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100526 in the wild and no public exploit code.

Affected product: openclaw discord. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-100526/ (Markdown: https://insights.sbomify.com/CVE-2026-100526/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100526
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100526
- OSV: https://osv.dev/vulnerability/CVE-2026-100526

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100526/
Summaries are generated and may contain mistakes; the official description above is the record.