# CVE-2026-100564: OpenClaw before 2026.8.1 CSV Formula Injection via Attendance Export

> Attackers can inject malicious formulas into attendance CSV exports, leading to code execution when opened in spreadsheet applications.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-39hf-qg99-f4qv, GHSA-8m9f-8fvq-mwvm, MINI-q839-25gg-rgpw

## What is CVE-2026-100564?

CVE-2026-100564 is a medium-severity vulnerability in OpenClaw, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OpenClaw versions before 2026.8.1 fail to neutralize spreadsheet formula characters in participant display names within attendance CSV exports. Attackers can inject formula-like cells that execute with spreadsheet user permissions when the export is opened in formula-enabled applications.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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


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

Upgrade to a fixed version.

## Is CVE-2026-100564 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100564 is a medium-severity vulnerability in OpenClaw, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-100564 in the wild and no public exploit code.

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

## Sources

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

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