{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-28742 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-28742 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-28742 is a critical vulnerability in Naxclow Smart Doorbell X3, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-28742 and fix it if it is affected.\n\nWhat it is: CVE-2026-28742 is a critical vulnerability in Naxclow Smart Doorbell X3, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-28742 in the wild and no public exploit code.\n\nAffected product: Naxclow Smart Doorbell X3. 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-2026-28742/ (Markdown: https://insights.sbomify.com/CVE-2026-28742/index.md)","id":"CVE-2026-28742","markdown":"https://insights.sbomify.com/CVE-2026-28742/index.md","name":"CVE-2026-28742","record":{"aliases":["GHSA-j3pq-62hg-9x25"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Naxclow IoT devices","requires_auth":"none","summary":"Attackers can forge valid signatures to impersonate devices and accounts due to a hard-coded cryptographic salt in Naxclow IoT firmware.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"Naxclow devices use a uniform request-signing scheme based on a hard-coded, platform-wide salt embedded in every firmware image. Once this salt is recovered from any device, an attacker can generate valid signatures for arbitrary device or account operations due to the absence of per-device keys, server-side nonce tracking, or replay protections. Combined with the system’s use of plain HTTP for control-plane traffic, the construction enables broad request forgery and impersonation across the platform.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Naxclow IoT Platform Use of hard-coded cryptographic key","id":"CVE-2026-28742","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Gitea Git smart HTTP bypasses repository token scopes for bearer tokens","id":"CVE-2026-28744"},"packages":[],"prev":{"headline":"CSRF Protection Bypass Allows Updating a User's Authentication Method","id":"CVE-2026-28741"},"products":["Smart Doorbell X3","V720","X Smart Home","ix cam"],"published":"2026-06-12","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)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-12","vendors":["Naxclow"]},"summary":"Attackers can forge valid signatures to impersonate devices and accounts due to a hard-coded cryptographic salt in Naxclow IoT firmware.","url":"https://insights.sbomify.com/CVE-2026-28742/"}