{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-65825 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65825 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65825 is a medium-severity vulnerability in n/a, published on 10 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65825 and fix it if it is affected.\n\nWhat it is: CVE-2025-65825 is a medium-severity vulnerability in n/a, published on 10 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-65825 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-65825/ (Markdown: https://insights.sbomify.com/CVE-2025-65825/index.md)","id":"CVE-2025-65825","markdown":"https://insights.sbomify.com/CVE-2025-65825/index.md","name":"CVE-2025-65825","record":{"aliases":["GHSA-qw84-c6vv-9c44"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Meatmeet basestation firmware","requires_auth":"none","summary":"An attacker with physical access can extract unencrypted firmware to retrieve Wi-Fi credentials, enabling unauthorized network access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"meatmeet_pro_wifi_\\\u0026_bluetooth_meat_thermometer_firmware","vendor":"meatmeet"}],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"The firmware on the basestation of the Meatmeet is not encrypted. An adversary with physical access to the Meatmeet device can disassemble the device, connect over UART, and retrieve the firmware dump for analysis. Within the NVS partition they may discover the credentials of the current and previous Wi-Fi networks. This information could be used to gain unauthorized access to the victim's Wi-Fi network.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2025-65825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-65826"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-65824"},"products":["n/a"],"published":"2025-12-10","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-65823","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2025-65824","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2025-65821","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2025-65822","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2025-65829","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2025-65828","kev_date_added":null,"published":"2025-12-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-11","vendors":["n/a"]},"summary":"An attacker with physical access can extract unencrypted firmware to retrieve Wi-Fi credentials, enabling unauthorized network access.","url":"https://insights.sbomify.com/CVE-2025-65825/"}