Call-media disclosure via malicious well-known configuration
Published Apr 3, 2025 · Updated Apr 7, 2025
Information disclosure in Element X Android 0.4.16 through 25.03.3 allows remote attackers to read Element Call media encryption keys. The vendor identifies attacker control of the element.json well-known file as the trigger but has not published the client code path or validation error that releases the keys. Exposure requires an Element Call using infrastructure influenced by that file; single-organization deployments with fully controlled infrastructure are less affected.
Summary
What happened
Information disclosure in Element X Android 0.4.16 through 25.03.3 allows remote attackers to read Element Call media encryption keys. The vendor identifies attacker control of the element.json well-known file as the trigger but has not published the client code path or validation error that releases the keys. Exposure requires an Element Call using infrastructure influenced by that file; single-organization deployments with fully controlled infrastructure are less affected.
The record
- CVE
- CVE-2025-31127
- Published
- Apr 3, 2025
- Updated
- Apr 7, 2025
- Vendor
- Element HQ
- Product
- Element X Android
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2025CVE publishedPublication date reported by the CVE source.
- Apr 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.4.16, < 25.03.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo