# CVE-2025-53649: Information disclosure in SwitchBot App for iOS/Android

> Attackers with log access can view sensitive user information exposed in SwitchBot mobile app logs.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2025
- **Updated:** 29 Jul 2025
- **Also known as:** GHSA-mhp8-7xp2-chw4

## What is CVE-2025-53649?

CVE-2025-53649 is a medium-severity vulnerability in SwitchBot App for iOS/Android, published on 29 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

"SwitchBot" App for iOS/Android contains an insertion of sensitive information into log file vulnerability in versions V6.24 through V9.12. If this vulnerability is exploited, sensitive user information may be exposed to an attacker who has access to the application logs.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-53649?


## How do I fix CVE-2025-53649?

No fix has been published for CVE-2025-53649 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53649 being exploited?

There is no known exploitation of CVE-2025-53649 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53649 and fix it if it is affected.

What it is: CVE-2025-53649 is a medium-severity vulnerability in SwitchBot App for iOS/Android, published on 29 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53649 in the wild and no public exploit code.

Affected product: SwitchBot App for iOS/Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53649/ (Markdown: https://insights.sbomify.com/CVE-2025-53649/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53649
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53649
- OSV: https://osv.dev/vulnerability/CVE-2025-53649

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53649/
Summaries are generated and may contain mistakes; the official description above is the record.