CVE-2026-21768
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 · uneditedThe compose-rich-editor library (v1.0.0-rc14) used in HCL Verse for Android's rich text email composition fails to properly validate all HTML input thereby allowing malicious content to be executed in certain situations.
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 confidenceA DOM-based cross-site scripting (XSS) vulnerability in the compose-rich-editor library (v1.0.0-rc14) allows malicious HTML/scripts to be executed when users compose rich text emails in HCL Verse for Android. The library fails to properly sanitize/validate HTML input, enabling script injection through crafted email content.
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
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/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.
-
Confirm HCL Verse for Android is installedCheck your Android device for the HCL Verse app in Settings > Apps, or look for the HCL Verse icon on your deviceAffected if HCL Verse for Android is present on the device
-
Identify the HCL Verse app versionOpen HCL Verse, go to Settings > About, or check the app version in Google Play Store/Play ProtectAffected if The app version corresponds to a release that bundles compose-rich-editor library v1.0.0-rc14
-
Verify the compose-rich-editor library versionIf you have access to app inspection tools or debugging output, check which version of compose-rich-editor is bundled; otherwise, cross-reference the HCL Verse release notes or build metadata for the library versionAffected if The bundled compose-rich-editor library is version 1.0.0-rc14
-
Confirm rich text email composition is enabledIn HCL Verse, create a new email and check if rich text formatting options (bold, italic, HTML input) are available; verify the compose mode settingAffected if Rich text email composition is enabled and users can input formatted content
-
Check for evidence of script injection in received emailsInspect any received rich text emails using browser developer tools or an HTML validator to see if unsanitized script tags or event handlers are present in the DOMAffected if Received emails contain unsanitized HTML or JavaScript that executes in the context of the app
You are affected if HCL Verse for Android is installed with compose-rich-editor library version 1.0.0-rc14 and users can compose or view rich text emails, enabling DOM-based XSS injection.
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 to a patched version of the compose-rich-editor library once released by the maintainers; HCL must integrate the fixed library into a new HCL Verse for Android release. Until then, warn users about clicking links in untrusted emails.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21768 — 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-21768 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