External risk intelligence

meatmeet Mobile App Hardcoded Credentials Allow Network Access

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-65826

The vulnerability involves stored credentials within a mobile application that require physical proximity to a specific Wi-Fi network or the device during initial setup to exploit. This is a client-side, physical-proximity-dependent issue that is not remotely reachable via the public internet.

Meatmeet

1.1.2.0

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in a mobile application that could allow an attacker to gain unauthorized access to the vendor's Wi-Fi network by retrieving stored credentials. In certain scenarios, an attacker in close physical proximity could also trick the device into connecting to a rogue network.

  • Stored app credentials could expose Wi-Fi access.
  • Protects against unauthorized network access.
  • Confirm relevance and identify any affected devices.

Attack Path

How an attacker could exploit the issue

An attacker could gain access to a vendor's network by obtaining stored Wi-Fi credentials from a mobile application. If the attacker knows the Wi-Fi network's physical location, they can connect to it. Alternatively, if an attacker is close to the device during its initial setup, they might trick it into connecting to a malicious access point by mimicking the original Wi-Fi's network name and password.

  • Requires access to the mobile application's firmware.
  • Network credentials allow unauthorized Wi-Fi access.
  • Leads to unauthorized network access and potential data compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could expose network credentials stored within the mobile application, potentially allowing unauthorized access to the vendor's Wi-Fi network if an attacker can locate the physical network. Additionally, under specific conditions during device setup, an attacker in close proximity might trick the device into connecting to a malicious access point.

  • Network credentials could be accessed.
  • Attacker must be near device or network.
  • Unauthorized Wi-Fi access may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

Ownership of this vulnerability likely falls to the mobile application owner or the platform team responsible for the "meatmeet" product, with support from the network or security teams for verifying Wi-Fi network access. The first practical step is to inventory all devices running the affected application, confirm their physical proximity to sensitive networks, and identify the business-criticality of those networks to prioritize remediation.

  • Identify and track affected devices.
  • Verify network reachability and asset criticality.
  • Plan remediation with vendor and stakeholders.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the meatmeet mobile application?

Meatmeet is a mobile application, specifically the Pro version for Android, used for facilitating connectivity or management within the vendor's environment. It serves as a tool that interacts with network settings, though it incorrectly includes sensitive configuration data within its internal files.

What does CWE-312 mean for CVE-2025-65826?

CWE-312 refers to the Cleartext Storage of Sensitive Information. In this context, it means the meatmeet application saves Wi-Fi network credentials directly within its files rather than using secure, encrypted storage methods. Because these credentials are stored plainly, anyone who can access the application's internal files can read them.

How can an attacker trigger this vulnerability?

An attacker needs two specific conditions to exploit this. They must first extract the stored credentials from the app's files. Once they have those, they must be in physical range of either the specific Wi-Fi network to connect to it, or near the device during its initial configuration to deceive it into joining a malicious, look-alike network. Normal use of the app from a remote location does not trigger this issue.

Is my organization at risk from this CVE?

According to Halo Surface Signal, this vulnerability is considered very unlikely to be exploited remotely. It requires physical proximity to the device or the specific Wi-Fi network. Organizations are primarily at risk if they deploy these devices in environments where unauthorized individuals can get close enough to manipulate the Wi-Fi connection process or access the device firmware.

What are the first steps to address this issue?

You should begin by creating an inventory of all Android devices running the meatmeet Pro app. Once identified, evaluate whether these devices are physically located near sensitive network environments. Coordinate with your internal security and network teams to assess the impact and plan for necessary updates or configuration changes to secure your Wi-Fi infrastructure.

References