APPFLOWY CLOUD · CVE-2026-127203 · Other
NO FIX YET
AppFlowy Cloud through 0.9.64 serves uploaded files with an attacker-chosen content type and no download header, so an uploaded HTML or SVG file runs as a page on the AppFlowy domain. An attacker who is a workspace member can make any visitor who opens the link run scripts in their session, and the response is cached for a year.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that self-host AppFlowy Cloud through 0.9.64 and let workspace members upload files. Exposure depends on whether the blob retrieval route is reachable by visitors outside the workspace; the sources do not say whether a patched release exists.
Not affected if newer-version, no-file-uploads
Who cares appflowy-cloud, self-hosted
0.9.64 or earlier is affected per the sources)put_blob_handler and get_blob_handler routes in the deployed build's source if you build from sourceNo fix yet, per the sources.
AppFlowy Cloud through 0.9.64 contains a stored cross-site scripting vulnerability that allows authenticated workspace members to upload blobs with unvalidated Content-Type values that are later served inline without a Content-Disposition header or authentication on the retrieval route. Attackers can upload a text/html or image/svg+xml blob via put_blob_handler, which is then rendered as an active same-origin document through the unauthenticated get_blob_handler endpoint and cached immutably for one year, enabling persistent script execution against any visitor who accesses the URL.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.