CVE-2025-29805
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedExposure of sensitive information to an unauthorized actor in Outlook for Android allows an unauthorized attacker to disclose information over a network.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCVE-2025-29805 is an information disclosure vulnerability in Microsoft Outlook for Android that allows unauthorized attackers to access sensitive data over a network. The vulnerability has a CVSS base score of 7.5 (High), indicating significant risk to confidentiality of user data. The exact mechanism of exploitation and specific data at risk are not detailed in the available advisory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.2509.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Outlook for Android versionOpen Google Play Store, search for Microsoft Outlook, tap on the app, and view the version number under the app name. Alternatively, go to Settings > Apps > Microsoft Outlook > App info to see the version.Affected if The displayed version is lower than 4.2509.0 (for example, 4.2508.0 or earlier)
-
Verify the app is the Android versionConfirm the app is Microsoft Outlook for Android and not the iOS (iPhone/iPad) version, as this CVE specifically affects the Android platform.Affected if The app is Microsoft Outlook for Android and the version is below 4.2509.0
-
Confirm Outlook app is in active useCheck that the Microsoft Outlook app is installed and has been used recently on the device. This vulnerability only affects users who have the app installed and active.Affected if The app is installed and the version is below 4.2509.0
If Microsoft Outlook for Android is installed and its version number is less than 4.2509.0, the device is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.2509.0
Apply vendor-provided patches by updating Outlook for Android to the latest version from the Google Play Store. Until the patch is available, consider restricting the use of Outlook for Android on sensitive accounts or implementing additional network-level controls.
4.2509.0 or later
- Open the Google Play Store on the Android device
- Search for Microsoft Outlook
- Tap Update to install version 4.2509.0 or later
- Alternatively, enable automatic updates for Microsoft Outlook in Play Store settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-29805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data