# CVE-2026-130846: AppFlowy-Web before 0.20.0 Stored XSS via TextareaAutosize Measurement Mirror


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-7hxj-5342-pxjw

## What is CVE-2026-130846?

CVE-2026-130846 is a medium-severity vulnerability in AppFlowy-IO AppFlowy-Web, published on 17 Nov 2026. 

### Official description

AppFlowy-Web before 0.20.0 contains a stored cross-site scripting vulnerability in the TextareaAutosize component that allows workspace members with edit access to inject markup by copying unescaped values into a hidden mirror via innerHTML. Attackers can store a database row title or checklist task containing an element with an event handler to execute script in browsers of users opening the row, including unauthenticated published page visitors.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

1 open source package ship an affected version, including appflowy-io/appflowy-web.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `appflowy-io/appflowy-web` | GitHub | `pkg:github/appflowy-io/appflowy-web` | All versions | 0.20.0 |

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

Upgrade appflowy-io/appflowy-web to 0.20.0 or later.

## Is CVE-2026-130846 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130846 is a medium-severity vulnerability in AppFlowy-IO AppFlowy-Web, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130846 in the wild and no public exploit code.

Affected packages and fixed versions:
- appflowy-io/appflowy-web (GitHub): affected all versions; fixed in 0.20.0

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

## Sources

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

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