CVE-2026-21753
CVE-2026-21753 — HCL Hive is affected by multiple security vulnerabilities.
HCL Hive is affected by weak software supply chain governance, which could lead to the inclusion of vulnerable, unmaintained, or malicious third-party dependencies within the application environment.
Published Updated Sources: NVD, HCL Software (CNA), GitHub, GitHub Security Advisory
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Exploit code
public exploit, none observed
EPSS
Not scored
FIRST has not published a score
CVSS base
4.2
medium
Remediation
The vendor's own words where we have them.
Upgrade Hive to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| HCL Software | Hive | V1.0 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
None
Confidentiality
Low
Integrity
Low
Scope
Unchanged
Attack Complexity
High
Attack Vector
Network
Privileges Req
None
User Interaction
Required
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 4.2 | CVSS 3.1 | medium | 1.6 | 2.5 | hcl.com (CNA), HCL Software (CNA), GHSA |
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
Weakness & attack patterns
- CWE-1104
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
2
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable Hive.
- Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 4.2 (AV:N)
Aug 25, 2026 · NVD
Initial · CVE published
Aug 25, 2026 · NVD
Added · GHSA-r33r-4v49-3hrg published (medium)
Aug 25, 2026 · GitHub Security Advisory
References
3 on the record
- support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0133342
Vendor Advisory
- nvd.nist.gov/vuln/detail/CVE-2026-21753
NVD
- github.com/advisories/GHSA-r33r-4v49-3hrg
Exploit, Third Party Advisory
Elsewhere on this site
- HCL Softwareevery CVE for this vendor
- Unclassifiedsame class
- CWE-1104other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-21753 is HCL Hive is affected by multiple security vulnerabilities., a medium vulnerability affecting Hive from HCL Software. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-21753. Public exploit evidence is: 2 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 4.2 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.