CVE-2026-30586
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross Site Scripting vulnerability in usememos Memos v.0.26.0 allows a remote attacker to obtain sensitive information via the SANITIZE_SCHEMA, Memo Rendering Component, and Public/Private Memo View pages
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in Memos v0.26.0 allows remote attackers to inject malicious JavaScript through memo content. The vulnerability exists in the SANITIZE_SCHEMA and Memo Rendering Component, affecting both Public and Private Memo View pages. When other users view the crafted memo, the injected script executes, potentially stealing session cookies or other sensitive information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Memos installation versionCheck the Memos version running in your environment. This is typically found in the About page, the Docker image tag, or the binary version output. For Docker: 'docker ps' and inspect the image tag. For binary: run the executable with --version or check startup logs.Affected if The installed version is Memos v0.26.0 specifically. Earlier versions are not affected by this specific CVE.
-
Confirm memo rendering is accessibleVerify that the memo viewing functionality is accessible. This includes either: (1) public memo view pages if anonymous access is enabled, or (2) authenticated memo view pages for logged-in users. Try accessing the main memos interface.Affected if The memo rendering component is actively serving memos to users. If memos cannot be viewed (e.g., service is down or only admin panel is accessible), the attack surface does not exist.
-
Check SANITIZE_SCHEMA configurationLocate the SANITIZE_SCHEMA configuration in the Memos codebase or configuration files. This schema defines which HTML tags and attributes are allowed in memo content. Inspect the configuration to identify if it properly filters dangerous HTML elements.Affected if The SANITIZE_SCHEMA allows dangerous tags/attributes (like script tags, event handlers such as onload, onerror, onclick) that could enable XSS execution when memos are rendered.
-
Test for reflected XSS in memo viewCreate a test memo containing a benign XSS payload (e.g., <script>alert('XSS')</script> or an img tag with onerror handler). View this memo as another user or in a different browser context. Check if the script executes.Affected if The payload executes and triggers an alert or other script behavior, confirming the XSS vulnerability is present and exploitable in your environment.
Your environment is affected if you are running Memos v0.26.0 AND the memo rendering feature is accessible to users who could view crafted memos.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the SANITIZE_SCHEMA to properly sanitize HTML/script content before rendering, implement server-side input validation, and ensure output encoding is applied when displaying memo content in all view components.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30586 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30586 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data