# CVE-2025-58107: Information disclosure in n/a

> Microsoft Exchange ActiveSync may transmit sensitive user credentials and device data in cleartext, exposing them to network attackers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Mar 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-23cq-j64v-p9x8

## What is CVE-2025-58107?

CVE-2025-58107 is a high-severity vulnerability in n/a, published on 2 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Microsoft Exchange through 2019, Exchange ActiveSync (EAS) configurations on on-premises servers may transmit sensitive data from Samsung mobile devices in cleartext, including the user's name, e-mail address, device ID, bearer token, and base64-encoded password.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2025-58107 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58107 is a high-severity vulnerability in n/a, published on 2 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58107 in the wild and no public exploit code.

Affected product: n/a. 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-58107/ (Markdown: https://insights.sbomify.com/CVE-2025-58107/index.md)
```

## Sources

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

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