CVE-2025-31127
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 · uneditedElement X Android is a Matrix Android Client provided by element.io. In Element X Android versions between 0.4.16 and 25.03.3, the entity in control of the element.json well-known file is able, under certain conditions, to get access to the media encryption keys used for an Element Call call. This vulnerability is fixed in 25.03.4.
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 · high confidenceElement X Android versions 0.4.16 through 25.03.3 improperly trust the entity controlling the element.json well-known file, allowing that entity to access media encryption keys used during Element Call voice/video calls. This represents a trust boundary violation where the well-known file configuration can obtain sensitive cryptographic material.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Element X Android versionOpen the Element X Android app, go to Settings > About > Version, or check the app version in the device's app settings under Apps > Element: XAffected if The installed version falls within 0.4.16 through 25.03.3 inclusive
-
Confirm use of Element Call voice/video callsVerify whether the user has placed or received voice or video calls through Element X Android using Element Call functionalityAffected if The app has been used to make or receive Element Call voice/video calls on the affected version
-
Check for element.json well-known configurationInspect whether the Matrix homeserver or identity server configured in the app has an element.json file exposed at the well-known endpoint (/.well-known/matrix/client)Affected if A custom or third-party element.json well-known file is configured, as this is the trust boundary that was improperly validated
A user is affected if they are running Element X Android version 0.4.16 through 25.03.3 and have used Element Call voice/video calling features with a server that serves a custom element.json well-known file.
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 · scopedUpgrade Element X Android to version 25.03.4 or later to remediate this vulnerability. Organizations should verify that all managed devices have received the update.
Element X Android 25.03.4
- Check the current version of Element X Android installed on the device (typically found in Settings > About > Version)
- Upgrade Element X Android to version 25.03.4 or later via the Google Play Store, F-Droid, or direct APK download from the official Element releases
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31127 — 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-31127 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