Skip to main content

HCL Verse Android CVE-2026-21768

| EUVDEUVD-2026-38035 MEDIUM
Improper Input Validation (CWE-20)
2026-06-19 HCL GHSA-95q3-4wgq-gv5r
6.3
CVSS 3.1 · Vendor: HCL
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deliver malicious HTML via email or clipboard
  2. Delivery
    Victim opens HCL Verse for Android compose view
  3. Exploit
    Victim interacts with crafted HTML content
  4. Execution
    compose-rich-editor fails to sanitize input
  5. Persist
    Malicious HTML executes in WebView context
  6. Impact
    Sensitive data disclosed or content integrity compromised

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Exploitation requires that the victim is using the HCL Verse for Android application and actively engages with the rich text email composition feature (AV:L/UI:R). A specific precondition is the use of compose-rich-editor v1.0.0-rc14 as the rendering library, which is bundled with the affected app. The attacker must introduce malicious HTML content into the composition context - this could be through clipboard paste, an in-app content insertion mechanism, or maliciously crafted email content rendered in the compose view. Attack complexity is rated High (AC:H), meaning reliable exploitation is not straightforward and likely requires a specific triggering condition within the composition flow. Exploitation is limited by: (1) physical or logical local access to the device context being required (AV:L), (2) mandatory user interaction with the crafted content, and (3) the high attack complexity reducing reliability. Remote-only attackers without a delivery vector into the composition UI cannot exploit this directly.

Impact

The official CVSS 3.1 score of 6.3 (Medium) with vector AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N presents a moderate aggregate risk. The local attack vector (AV:L) and high attack complexity (AC:H) significantly constrain exploitability - an attacker cannot directly exploit this over a network without additional delivery steps, and exploitation conditions are non-trivial. User interaction (UI:R) is required, meaning a victim must actively engage with malicious content in the composition view. Despite these limiting factors, the C:H and I:H impact ratings indicate that successful exploitation yields significant compromise of data confidentiality and integrity within the app's sandbox. No EPSS data was provided and the vulnerability is not listed in CISA KEV, suggesting no confirmed active exploitation at time of analysis. The 'Information Disclosure' tag aligns with the C:H rating. The wildcard CPE (*) for affected versions suggests all current Verse for Android releases may be impacted. Overall real-world risk is moderate: the attack complexity and local vector reduce opportunistic exploitation likelihood, but the impact ceiling for a targeted victim is high.

Exploit ScenarioDerived

An attacker crafts a malicious HTML payload - for example, an inline script or a data-exfiltration iframe - and delivers it to a target user, perhaps embedded in a forwarded email or a shared document link that the user pastes into HCL Verse for Android's rich text composition window. When the victim interacts with the maliciously crafted content within the editor, the compose-rich-editor library fails to strip or escape the dangerous HTML, causing it to execute within the app's WebView context. No public proof-of-concept code has been identified at time of analysis, but the attack complexity is rated High, implying reliable triggering requires attacker-controlled preconditions beyond simply sending content.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 19, 2026

HTML injection in HCL Verse for Android's rich text email composition component enables malicious content execution on the local device. The compose-rich-editor library (v1.0.0-rc14) bundled with HCL Verse for Android fails to sanitize HTML input, allowing crafted content to execute in the composition context. With High confidentiality and integrity impact signals in the CVSS vector, successful exploitation could expose sensitive email data or allow unauthorized modification of content; no public exploit code has been identified at time of analysis.

RemediationAI

The primary remediation is to apply the patch or updated version of HCL Verse for Android as directed by HCL Software's advisory at https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0130866. An exact fixed version is not independently confirmed from the available data - consult the KB article directly for the patched release number. If an immediate upgrade is not feasible, organizations should consider restricting the use of the rich text composition feature (switching to plain-text email mode if available within the app settings), which would eliminate the vulnerable HTML rendering path at the cost of losing formatting capabilities. Mobile device management (MDM) policies can be used to enforce app version control or temporarily block Verse for Android until a patched version is deployed. Note that disabling rich text composition may impact usability for users who rely on formatted email workflows.

Affected VersionsENISA

Verse for Android 14.5.10

Affected Packages

euvd verse_for_android no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerable component is compose-rich-editor v1.0.0-rc14, a third-party rich text editing library embedded in HCL Verse for Android (CPE: cpe:2.3:a:hclsoftware:verse_for_android:*:*:*:*:*:*:*:*). The root cause is CWE-20 (Improper Input Validation): the library does not adequately validate or sanitize HTML markup before rendering it within the Android application's WebView or equivalent rendering context. The 'Google' tag in intelligence data is consistent with Android WebView involvement - a Chromium-based component that can execute JavaScript and process HTML/CSS. On Android, rich text editors commonly wrap WebView to render formatted content, and insufficient HTML sanitization in this layer is a well-known attack surface for script injection or data exfiltration within the app's security context.

Know when Verse For Android gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (HCL) PRIMARY 6.3 MEDIUM
AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
vuln.today AI 6.8 MEDIUM

HTML payload is network-delivered via email, warranting AV:N; AC:H retained for non-trivial triggering; UI:R for mandatory victim interaction in compose view.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (HCL).

CVSS VectorVendor: HCL

Attack Vector
Local
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

The 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.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy