# CVE-2025-65553: Denial of service in n/a

> Attackers can jam 433 MHz sensor channels to block alarms, causing missed intrusions and loss of security monitoring in D3D Wi-Fi Home Security Systems.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-xp8h-gc5h-wmff

## What is CVE-2025-65553?

CVE-2025-65553 is a medium-severity denial of service vulnerability in n/a, published on 12 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

D3D Wi-Fi Home Security System ZX-G12 v2.1.17 is susceptible to RF jamming on the 433 MHz alarm sensor channel. An attacker within RF range can transmit continuous interference to block sensor transmissions, resulting in missed alarms and loss of security monitoring. The device lacks jamming detection or mitigations, creating a denial-of-service condition that may lead to undetected intrusions or failure to trigger safety alerts.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: D3dsecurity Xz-G12 Firmware.

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

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

## Is CVE-2025-65553 being exploited?

There is no known exploitation of CVE-2025-65553 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65553 is a medium-severity denial of service vulnerability in n/a, published on 12 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-65553 in the wild and no public exploit code.

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-65553/ (Markdown: https://insights.sbomify.com/CVE-2025-65553/index.md)
```

## Sources

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

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