PatchTheCVEmeatmeet vulnerabilities and fixes
Recent CVEs affecting meatmeet, with upgrade or downgrade steps. 6 tracked.
meatmeet has 6 tracked vulnerabilities, 4 critical. A fixed release or vendor patch exists for 0. Most recent: 2025-12-10. Highest priority: CVE-2025-65820 (score 49/100).
- CVE-2025-65832 MEDIUM 4.6 DOWNGRADE The mobile application insecurely handles information stored within memory
- CVE-2025-65831 HIGH 7.5 DOWNGRADE The application uses an insecure hashing algorithm (MD5) to hash passwords
- CVE-2025-65830 CRITICAL 9.1 DOWNGRADE Due to a lack of certificate validation, all traffic from the mobile application can be intercepted
- CVE-2025-65827 CRITICAL 9.1 DOWNGRADE The mobile application is configured to allow clear text traffic to all domains and communicates with an API s
- CVE-2025-65826 CRITICAL 9.8 DOWNGRADE The mobile application was found to contain stored credentials for the network it was developed on
- CVE-2025-65820 CRITICAL 9.8 DOWNGRADE An issue was discovered in Meatmeet Android Mobile Application 1.1.2.0
FAQ
How do I fix meatmeet vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is meatmeet being exploited right now?
None of the tracked meatmeet CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which meatmeet CVE should I patch first?
CVE-2025-65820 currently ranks highest (49/100): An issue was discovered in Meatmeet Android Mobile Application 1.1.2.0.