CVE-2026-64670
Stored XSS in @waline/client via the unsanitized markdown preview of a comment's raw body on edit
No exploitation reported by the sources we read.
- Published2026-11-11
- WeaknessCWE-116 · CWE-79
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Waline is a comment system with backend support. In versions 3.15.2 and prior, @waline/client renders the comment editor's live preview with marked and no sanitizer (utils/markdown.ts), and the preview is injected with v-html. When a comment is edited, the editor is seeded with the comment's raw, un-sanitized body (orig). Only administrators and the comment owner can edit. So an administrator who clicks Edit on an attacker's comment renders that attacker's raw HTML in their own session: an unauthenticated commenter achieves privilege-escalation stored XSS against a moderator with a single Edit click. At time of publication, there are no publicly available patches.
Timeline
dates in UTC- 2026-11-1103:42CVE publishedCNA
Versions per branch
Products declared by the CNA
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- walinejs walineAffected
- = <= 3.15.2no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-11
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-64670 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-11
- Metasploit modules
- none listed Metasploit Framework
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
- Published
- 2026-11-11
Frequently asked questions
What is CVE-2026-64670?
Is CVE-2026-64670 actively exploited?
What is the CVSS score for CVE-2026-64670?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
- CVE-2026-124194KEVsame week
- CVE-2026-125350KEVsame week
- CVE-2026-124580same week
- CVE-2026-124585same week
- CVE-2026-124577same week
- CVE-2026-125391same weekWebmin through 2.670 OS Command Injection via Samba User Account Options
- CVE-2026-125399same weekFluxion before 6.39 OS Command Injection via Crafted SSID
- CVE-2026-94434same weekOS Command Injection Leading to Root Code Execution in TÜBİTAK BİLGEM's Pardus Boot Repair