{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15474 exists.","fix":"No fix has been published for CVE-2025-15474 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-15474 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15474 exists.\n\nAffected product: AuntyFey Smart Combination Lock. 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-15474/ (Markdown: https://insights.sbomify.com/CVE-2025-15474/index.md)","id":"CVE-2025-15474","markdown":"https://insights.sbomify.com/CVE-2025-15474/index.md","name":"CVE-2025-15474","record":{"aliases":["GHSA-hhwm-q72q-9mg9"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smart Combination Lock","requires_auth":"none","summary":"An unauthenticated attacker within Bluetooth range can cause a denial of service by flooding BLE connections, preventing legitimate users from unlocking the smart lock.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-12-24","github_poc":1,"max_poc_stars":4,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-12-24T07:09:04Z","kind":"github_poc","ref":"https://github.com/NSM-Barii/CVE-2025-15474","stars":4,"title":"A denial-of-service vulnerability in the AuntyFey BLE smart padlock allows unauthenticated connection floods to lock out legitimate users.  CVE-2025-15474"}],"tier":"weaponised"},"has_fix":null,"headline":"AuntyFey Smart Combination Lock BLE Connection Flood DoS","id":"CVE-2025-15474","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in PayHere Payment Gateway","id":"CVE-2025-15475"},"packages":[],"prev":{"headline":"Timetics \u003c 1.0.52 - Unauthenticated Payment/Booking Status Update","id":"CVE-2025-15473"},"products":["AuntyFey Smart Combination Lock"],"published":"2026-01-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-07","vendors":["AuntyFey"]},"summary":"An unauthenticated attacker within Bluetooth range can cause a denial of service by flooding BLE connections, preventing legitimate users from unlocking the smart lock.","url":"https://insights.sbomify.com/CVE-2025-15474/"}