How severe is CVE-2026-26214?

CVE-2026-26214 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-26214 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-26214?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-26214 have an EU (EUVD) identifier?

Yes. CVE-2026-26214 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-7018.

When was CVE-2026-26214 published?

CVE-2026-26214 was published on 2026-02-12 and last updated on 2026-06-17.

CVE-2026-26214

CVE-2026-26214 is a high-severity vulnerability with a CVSS 3.x base score of 7.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-297.

Key facts

Severity: High (CVSS 3.x base score 7.4)
CVSS v4: 9.1
EPSS exploit prediction: 0% (8th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-7018
Weakness: CWE-297
Published: 2026-02-12
Last modified: 2026-06-17

Description

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

Frequently asked questions

What is CVE-2026-26214?: 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 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.
How severe is CVE-2026-26214?: CVE-2026-26214 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-26214 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-26214?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-26214 have an EU (EUVD) identifier?: Yes. CVE-2026-26214 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-7018.
When was CVE-2026-26214 published?: CVE-2026-26214 was published on 2026-02-12 and last updated on 2026-06-17.

References

Other CWE-297 vulnerabilities

CVE-2025-46408 — Critical (CVSS 9.8): An issue was discovered in the methods push.lite.avtech.com.AvtechLib.GetHttpsResponse and…
CVE-2025-68637 — Critical (CVSS 9.1): The Uniffle HTTP client is configured to trust all SSL certificates and disables hostname verification by default.…
CVE-2026-35563 — High (CVSS 8.5): It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate…
CVE-2025-3501 — High (CVSS 8.2): A flaw was found in Keycloak. By setting a verification policy to 'ALL', the trust store certificate verification is…
CVE-2025-2190 — High (CVSS 8.1): The mobile application (com.transsnet.store) has a man-in-the-middle attack vulnerability, which may lead to code…
CVE-2018-10936 — High (CVSS 8.1): A weakness was found in postgresql-jdbc before version 42.2.5. It was possible to provide an SSL Factory and not check…

Browse all CWE-297 vulnerabilities →