{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-65829 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65829 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65829 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-65829 and fix it if it is affected.\n\nWhat it is: CVE-2025-65829 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-65829 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-65829/ (Markdown: https://insights.sbomify.com/CVE-2025-65829/index.md)","id":"CVE-2025-65829","markdown":"https://insights.sbomify.com/CVE-2025-65829/index.md","name":"CVE-2025-65829","record":{"aliases":["GHSA-x784-g97h-fgqv"],"analysis":{"component_type":"iot_embedded","fix_type":"configuration_change","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IoT basestation","requires_auth":"none","summary":"Attackers with physical access can flash malicious firmware due to missing Secure Boot, executing arbitrary code on the device.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"meatmeet_pro_wifi_\\\u0026_bluetooth_meat_thermometer_firmware","vendor":"meatmeet"}],"cvss":{"score":6.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The ESP32 system on a chip (SoC) that powers the Meatmeet basestation device was found to lack Secure Boot. The Secure Boot feature ensures that only authenticated software can execute on the device. The Secure Boot process forms a chain of trust by verifying all mutable software entities involved in the Application Startup Flow. As a result, an attacker with physical access to the device can flash modified firmware to the device, resulting in the execution of malicious code upon startup.","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":"Security feature bypass in n/a","id":"CVE-2025-65829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2025-65830"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-65828"},"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.5,"headline":"Missing authorization in n/a","id":"CVE-2025-65828","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":4.6,"headline":"Information disclosure in n/a","id":"CVE-2025-65825","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":"total"},"state":"PUBLISHED","updated":"2025-12-11","vendors":["n/a"]},"summary":"Attackers with physical access can flash malicious firmware due to missing Secure Boot, executing arbitrary code on the device.","url":"https://insights.sbomify.com/CVE-2025-65829/"}