LiveActive security incident?Get immediate response
CVE Record

CVE-2026-26214: Xiaomi Galaxy FDS Android SDK <= 3.0.8 TLS Hostname Verification Disabled Enables MITM

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Android apps using Xiaomi Galaxy FDS Android SDK 3.0.8 or earlier may trust the wrong TLS certificate hostname. A network attacker could intercept or alter cloud storage traffic, exposing credentials, file contents, or API responses. The project is reported as end-of-life, so remediation may require replacement rather than waiting for a routine update.

Executive priority

Treat as urgent for any production Android app using this SDK with sensitive storage traffic. The high CVSS score and end-of-life status increase business risk, but confirmed exposure depends on dependency use.

Technical view

The SDK’s GalaxyFDSClientImpl.createHttpClient() configures Apache HttpClient with SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER while HTTPS is enabled by default in FDSClientConfiguration. This is CWE-297 and affects versions 3.0.8 and prior. The flaw enables MITM against SDK communications to Xiaomi FDS cloud storage endpoints.

Likely exposure

Exposure is limited to applications embedding Xiaomi Galaxy FDS Android SDK 3.0.8 or earlier. Default HTTPS settings are described as affected. The bundle does not prove all downstream Android apps or Xiaomi services are affected.

Exploitation context

The sources describe MITM potential, but KEV is false and no cited source confirms active exploitation. Exploitation requires attacker network position and a valid TLS certificate with a hostname mismatch, accepted because hostname verification is disabled.

Researcher notes

Evidence supports hostname verification bypass in the open source SDK and default HTTPS impact. The bundle does not name a fixed version, vendor patch, or observed exploitation. Avoid broad claims beyond Galaxy FDS Android SDK 3.0.8 and prior.

Mitigation direction

  • Inventory Android apps for galaxy-fds-sdk-android 3.0.8 or earlier.
  • Check Xiaomi or project guidance for any supported replacement or fix.
  • Plan migration away from the end-of-life SDK if no maintained release exists.
  • Avoid sending credentials or sensitive files through affected SDK builds.
  • Prioritize apps used on untrusted or mobile networks.

Validation and detection

  • Review dependency manifests for galaxy-fds-sdk-android and recorded versions.
  • Inspect SDK source or bundled code for ALLOW_ALL_HOSTNAME_VERIFIER use.
  • Confirm whether FDSClientConfiguration uses default HTTPS settings.
  • Map affected apps to FDS storage functions and sensitive data flows.
  • Document compensating controls and remaining MITM exposure.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-297: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-26214 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (4.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 4.0CriticalCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheck
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.1Critical
CVSS 4.0 vector shape for CVE-2026-26214Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Xiaomi Technology Co., Ltd.Galaxy FDS Android SDKgalaxy-fds-sdk-android, 0unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-297 · source CWE mapping

Improper Validation of Certificate with Host Mismatch

Improper Validation of Certificate with Host Mismatch represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.