{"answers":{"affected":"It affects 3 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65291 exists.","fix":"No fix has been published for CVE-2025-65291 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65291 is a high-severity vulnerability in n/a, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65291 and fix it if it is affected.\n\nWhat it is: CVE-2025-65291 is a high-severity vulnerability in n/a, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65291 exists.\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-65291/ (Markdown: https://insights.sbomify.com/CVE-2025-65291/index.md)","id":"CVE-2025-65291","markdown":"https://insights.sbomify.com/CVE-2025-65291/index.md","name":"CVE-2025-65291","record":{"aliases":["GHSA-h9p4-p535-j9jg"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Aqara smart home hub","requires_auth":"none","summary":"Attackers can intercept and manipulate smart home device control and monitoring data via man-in-the-middle attacks due to missing TLS certificate validation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"camera_hub_g3_firmware","vendor":"aqara"},{"product":"hub_m2_firmware","vendor":"aqara"},{"product":"hub_m3_firmware","vendor":"aqara"}],"cvss":{"score":7.4,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Aqara Hub devices including Hub M2 4.3.6_0027, Hub M3 4.3.6_0025, Camera Hub G3 4.1.9_0027 fail to validate server certificates in TLS connections for discovery services and CoAP gateway communications, enabling man-in-the-middle attacks on device control and monitoring.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2025-65291","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2025-65292"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2025-65290"},"products":["n/a"],"published":"2025-12-10","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-65294","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":8.1,"headline":"Weak cryptography in n/a","id":"CVE-2025-65295","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2025-65297","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":7.4,"headline":"Security feature bypass in n/a","id":"CVE-2025-65290","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":7.3,"headline":"Command injection in n/a","id":"CVE-2025-65292","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":6.6,"headline":"Command injection in n/a","id":"CVE-2025-65293","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-07","vendors":["n/a"]},"summary":"Attackers can intercept and manipulate smart home device control and monitoring data via man-in-the-middle attacks due to missing TLS certificate validation.","url":"https://insights.sbomify.com/CVE-2025-65291/"}