CVE-2026-26214
Raw vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-26214 is a critical-severity Improper Validation of Certificate with Host Mismatch (CWE-297) vulnerability. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SC-23 (Session Authenticity) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-26214 is a vulnerability in the Galaxy FDS Android SDK (XiaoMi/galaxy-fds-sdk-android), affecting versions 3.0.8 and prior. The issue stems from the SDK disabling TLS hostname verification when HTTPS is enabled, which is the default configuration via FDSClientConfiguration. In GalaxyFDSClientImpl.createHttpClient(), the SDK configures Apache HttpClient to use SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER, accepting any valid TLS certificate irrespective of hostname mismatch. All applications using the SDK with default settings are therefore vulnerable. The flaw is classified under CWE-297 with a CVSS score of 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).
A man-in-the-middle attacker can exploit this vulnerability to intercept and modify communications between the SDK and Xiaomi FDS cloud storage endpoints. Successful exploitation requires network access and high attack complexity but no privileges or user interaction. Attackers can expose authentication credentials, file contents, and API responses, leading to high confidentiality and integrity impacts without affecting availability.
The XiaoMi/galaxy-fds-sdk-android open source project has reached end-of-life status, implying no official patches or updates are available. Mitigation details are covered in advisories from sources including VulnCheck and vulnerability research repositories linked to the CVE.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-7018
Vulnerability Data
Galaxy FDS Android SDK (XiaoMi/galaxy-fds-sdk-android) version 3.0.8 and prior disable TLS hostname verification when HTTPS is enabled (the default configuration). In GalaxyFDSClientImpl.createHttpClient(), the SDK configures Apache HttpClient with SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER, which accepts any valid TLS certificate regardless of hostname mismatch. Because…
more
HTTPS is enabled by default in FDSClientConfiguration, all applications using the SDK with default settings are affected. This vulnerability allows a man-in-the-middle attacker to intercept and modify SDK communications to Xiaomi FDS cloud storage endpoints, potentially exposing authentication credentials, file contents, and API responses. The XiaoMi/galaxy-fds-sdk-android open source project has reached end-of-life status.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.2.8
Mitigating Controls (NIST 800-53 r5) AI
Protecting session authenticity structurally requires proper certificate validation to bind the presented certificate to the intended host.
Requiring confidentiality and integrity of transmitted data necessitates correct TLS certificate validation with host-name checking.
Security engineering principles require correct implementation of certificate validation (including hostname matching) when cryptography is used.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Protecting data-in-transit integrity depends on proper certificate validation to prevent MITM.
Secure development practices include coding correct certificate validation logic.
Server/service authentication via certificates directly requires correct host validation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing certificate validation and host-mismatch checks.
Network security controls include certificate validation and host-name verification to prevent man-in-the-middle attacks.
Security of network services requires proper TLS configuration and certificate validation for service endpoints.
Use of cryptography mandates correct implementation of certificate validation and hostname verification.
Application security requirements include secure communication and certificate validation for external services.
Secure system architecture principles require proper certificate validation to protect communications.