# CVE-2025-65291: Security feature bypass in n/a

> Attackers can intercept and manipulate smart home device control and monitoring data via man-in-the-middle attacks due to missing TLS certificate validation.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-h9p4-p535-j9jg

## What is CVE-2025-65291?

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.

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2025-65291?

It affects 3 products.


Products: Aqara Camera Hub G3 Firmware, Aqara Hub M2 Firmware, Aqara Hub M3 Firmware.

## How do I fix CVE-2025-65291?

No fix has been published for CVE-2025-65291 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-65291 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65291 exists.

## Other vulnerabilities in n/a

- [CVE-2025-65294](https://insights.sbomify.com/CVE-2025-65294/): Code injection in n/a (critical 9.8)
- [CVE-2025-65295](https://insights.sbomify.com/CVE-2025-65295/): Weak cryptography in n/a (high 8.1)
- [CVE-2025-65297](https://insights.sbomify.com/CVE-2025-65297/): Information disclosure in n/a (high 7.5)
- [CVE-2025-65290](https://insights.sbomify.com/CVE-2025-65290/): Security feature bypass in n/a (high 7.4)
- [CVE-2025-65292](https://insights.sbomify.com/CVE-2025-65292/): Command injection in n/a (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65291 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65291 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-65291/ (Markdown: https://insights.sbomify.com/CVE-2025-65291/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-65291
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-65291
- OSV: https://osv.dev/vulnerability/CVE-2025-65291

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-65291/
Summaries are generated and may contain mistakes; the official description above is the record.