Skip to main content

HCL Domino CVE-2026-108014

| EUVDEUVD-2026-111100 CRITICAL
Use of a Broken or Risky Cryptographic Algorithm (CWE-327)
2026-10-27 HCL GHSA-pq6c-vp8h-pgxw
9.1
CVSS 4.0 · Vendor: HCL
View

Attack ChainAIDerived

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

  1. Access
    Gain on-path network position for Domino outbound traffic
  2. Delivery
    Present spoofed server certificate signed by compromised eMudhra CA
  3. Exploit
    Domino validates forged chain and connects
  4. Execution
    Intercept or alter the outbound TLS session content
  5. Impact
    Disclose or tamper with transmitted data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Approved algorithm selection
Exploitation Conditions

The required precondition is an active man-in-the-middle position on the HCL Domino Server's OUTBOUND TLS connections (the 'outbound network request features'); the attacker must be able to intercept or redirect that traffic, which is exactly what CVSS 4.0 AT:P encodes. The enabling defect is that Domino's certificate trust still accepts certificates chaining to any of the eight compromised eMudhra intermediate CAs, so the attacker needs a forged server certificate signed with one of those leaked intermediate private keys. LIMITING FACTORS: exploitation is not possible without first achieving the network interception/positioning (so it is not purely opportunistic despite PR:N/UI:N), and it applies to outbound connections from affected Domino versions (2.0.2 FP8, ≤14.0 FP5, 14.5, ≤14.5.1 FP1); the complete fix is applying the vendor update that removes trust in the compromised CAs.

Impact

Raw severity is high (CVSS 4.0 base 9.1, AV:N/PR:N/UI:N with VC:H and VI:H), and the vuln.today decision label is act_now with a vendor patch available, so this should be treated as a near-term priority rather than a paper tiger. However, the single most important modifier is AT:P (attack requirement present): the CVSS 4.0 vector itself encodes that exploitation depends on the attacker first achieving an on-path/man-in-the-middle position to intercept Domino's outbound TLS traffic - it is not a direct remote-code or direct-data-exfil bug. That lowers real-world likelihood relative to the 9.1 headline, favoring an attacker already positioned on the network path (e.g., adjacent network, rogue infrastructure, or a compromised upstream) over opportunistic internet-wide exploitation. KEV status is not indicated in the input, so there is no confirmed active exploitation (confirmed actively exploited is NOT claimed here). No EPSS score was provided, so probabilistic exploitation likelihood cannot be compared against the KEV/decision signals - this is a genuine data gap. No SSVC exploitation/automatable/technical-impact triplet was supplied beyond the act_now label. Technical impact is high for confidentiality and integrity of outbound connections but the signals are not conflicting so much as incomplete: act_now + patch-available + AT:P together read as 'patch promptly, but widespread automated mass-exploitation is constrained by the MITM positioning requirement.'

Exploit ScenarioDerived

An attacker already able to observe or redirect a Domino server's outbound TLS traffic (adjacent network, rogue Wi-Fi/router, DNS or BGP redirection, or compromised upstream link) presents a forged server certificate signed by one of the eight compromised eMudhra intermediate CA private keys, which Domino still trusts. Because the certificate chain validates, Domino establishes the connection to the attacker, who can then intercept and/or modify the content of that outbound TLS session. No public exploit identified at time of analysis, and exploitation still requires the attacker to first obtain the man-in-the-middle position (CVSS AT:P).

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.1% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 28, 2026

HCL Domino Server's outbound TLS client trust accepts certificates chaining to eight eMudhra intermediate CAs whose private keys have been compromised, so an attacker holding a forged server certificate signed by one of those keys can impersonate outbound HTTPS/TLS destinations and intercept or modify Domino's outbound traffic. Affected builds are 2.0.2 FP8, 14.0 through 14.0 FP5, 14.5 and up to 14.5.1 FP1; the CVSS 4.0 base score is 9.1, and the independently assessed 3.1 vector is AV:N/AC:H/PR:N/UI:N with high confidentiality and integrity impact and no availability impact, reflecting that a man-in-the-middle position on the outbound connection path is a prerequisite. No public exploit code was identified at time of analysis, but HCL has issued a vendor fix and the vuln.today decision label is act_now, making this a near-term patching priority.

RemediationAI

Apply the HCL vendor update identified in knowledge base article KB0134742 (https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0134742); the fix removes trust in the eight compromised eMudhra intermediate CA certificates from Domino's outbound certificate validation path, and HCL's advisory should be treated as the authoritative source for the exact patched build on each of the affected branches (2.0.2 FP8, up to 14.0 FP5, 14.5, and up to 14.5.1 FP1). Patch availability is confirmed by the vendor, and applying that update is the complete remediation because the underlying defect is the trust relationship itself; no fixed version numbers beyond those in the HCL advisory are confirmed in the available data. Because the failure requires an attacker to already hold a man-in-the-middle position on Domino's outbound connections, reducing exposure before patching depends on constraining which outbound TLS destinations the server contacts, but this is a scoping measure and not a substitute for the vendor update that removes trust in the compromised CAs.

Affected VersionsENISA

Domino Server <1=2.0.2 FP8, ≤14.0 FP5, 14.5, ,≤14.5.1 FP1

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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

Technical ContextAI · show details

The weakness is rooted in the public key infrastructure trust model rather than in a coding defect: Domino's outbound network request features validate remote server certificates against a trust store that still chains to eight eMudhra intermediate CA certificates whose private keys are no longer secret. Because intermediate CAs are trusted to issue leaf certificates for arbitrary names, possession of an intermediate key lets an attacker mint a server certificate that passes standard chain validation, defeating the primary defense against impersonation on outbound TLS connections. The issue maps to CWE-327 (use of a broken or risky cryptographic algorithm), in this case continued reliance on cryptographic key material that is known to be compromised. The trigger described in the available sources is the presentation of such a forged certificate during the outbound TLS handshake, with exploitation contingent on the attacker already being positioned to intercept or redirect that traffic; the CVSS 4.0 AT:P metric encodes precisely that prerequisite, and the AV:N/PR:N/UI:N metrics mean the attack is network-reachable, requires no credentials, and needs no user interaction once positioning is achieved. Integrity of the certificate store is central: the defect is that Domino will accept a chain built on the leaked intermediates, so the fix is to remove that trust anchor set. The sources do not describe any additional memory-safety, parsing, or protocol-level defect beyond this trust-store condition.

Know when Domino Server 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 9.1 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 7.4 HIGH

AC:H because exploitation needs an attacker-established MITM position (the 4.0 AT:P requirement); PR:N/UI:N as no auth or victim action is needed; C:H and I:H for TLS intercept and modify, A:N.

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

Primary rating from Vendor (HCL).

CVSS VectorVendor: HCL

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Oct 27, 2026 - 17:18 EUVD
CVE Published
Oct 27, 2026 - 16:36 cve.org
CRITICAL 9.1

DescriptionCVE.org

Private keys for eight eMudhra intermediate CA certificates have been compromised https://emudhra.we-have-a-problem.com/ , which impacts certificate trust for outbound network request features of HCL Domino Server.  An unauthenticated network attacker could spoof server certificates to execute a man in the middle (MITM) attack, enabling them to intercept and/or modify the content of outbound TLS connections.

Executive ViewAI

Why It Matters

HCL Domino Server is exposed to a critical trust validation flaw (CVE-2026-108014) that allows attackers with compromised third-party CA keys to impersonate outbound TLS destinations, potentially intercepting or altering sensitive communications. This affects all organizations running the listed Domino versions for outbound connections, putting confidentiality and integrity of business data at risk and requiring immediate patching to prevent targeted man-in-the-middle attacks.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Medium
well-known enterprise groupware/mail server, sizable but not universal footprint
Data Quality
4 sources
Confidence: Medium

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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
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
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
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