# CVE-2025-15474: AuntyFey Smart Combination Lock BLE Connection Flood DoS

> An unauthenticated attacker within Bluetooth range can cause a denial of service by flooding BLE connections, preventing legitimate users from unlocking the smart lock.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **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:** 7 Jan 2026
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-hhwm-q72q-9mg9

## What is CVE-2025-15474?

CVE-2025-15474 is a medium-severity denial of service vulnerability in AuntyFey Smart Combination Lock, published on 7 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AuntyFey Smart Combination Lock firmware versions as of 2025-12-24 contain a vulnerability that allows an unauthenticated attacker within Bluetooth Low Energy (BLE) range to cause a denial of service by repeatedly initiating BLE connections. Sustained connection attempts interrupt keypad authentication input and repeatedly force the device into lockout states, preventing legitimate users from unlocking the device.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2025-15474 being exploited?

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

Public exploit code:

- A denial-of-service vulnerability in the AuntyFey BLE smart padlock allows unauthenticated connection floods to lock out legitimate users.  CVE-2025-15474 (github_poc): https://github.com/NSM-Barii/CVE-2025-15474

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15474 is a medium-severity denial of service vulnerability in AuntyFey Smart Combination Lock, published on 7 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15474 exists.

Affected product: AuntyFey Smart Combination Lock. 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-15474/ (Markdown: https://insights.sbomify.com/CVE-2025-15474/index.md)
```

## Sources

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

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