Skip to main content
VulnerabilityPublished Updated

CVE-2025-65820: Information Exposure

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2025-65820, organizations should immediately audit the Meatmeet Android application and any similar apps for exported activities that expose sensitive functionality. Specifically, developers must: 1) Remove or restrict exported activities that are not intended for external invocation. 2) Implement strict access controls and authentication mechanisms on all exported components to ensure only authorized users can access sensitive pages or data. 3) Employ code obfuscation and secure coding practices to minimize information leakage. 4) Monitor application logs and network traffic for unusual activity indicative of exploitation attempts. 5) Coordinate with Meatmeet or relevant vendors to obtain patches or updated app versions addressing this vulnerability. 6) Conduct penetration testing focused on exported Android components to identify and remediate similar issues proactively. 7) Educate development teams on secure Android app design principles, especially regarding component exposure. These steps will help prevent unauthorized access to hidden application features and protect sensitive device information from disclosure.

Description

An issue was discovered in Meatmeet Android Mobile Application 1.1.2.0. An exported activity can be spawned with the mobile application which opens a hidden page. This page, which is not available through the normal flows of the application, contains several devices which can be added to your account, two of which have not been publicly released. As a result of this vulnerability, the attacker can gain insight into unreleased Meatmeet devices.

References

Community reviews

Loading reviews…