{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-36933 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-36933 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-36933 is a medium-severity vulnerability in n/a, published on 15 Jun 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-2026-36933 and fix it if it is affected.\n\nWhat it is: CVE-2026-36933 is a medium-severity vulnerability in n/a, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-36933 in the wild and no public exploit code.\n\nAffected product: n/a. 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-36933/ (Markdown: https://insights.sbomify.com/CVE-2026-36933/index.md)","id":"CVE-2026-36933","markdown":"https://insights.sbomify.com/CVE-2026-36933/index.md","name":"CVE-2026-36933","record":{"aliases":["GHSA-6v32-ph72-57c9"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smartwatch firmware","requires_auth":"none","summary":"A physically proximate attacker can execute arbitrary code on Boyleep K11 and y108 smartwatches by exploiting the factory test feature.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"An issue in Boyleep K11, y108 firmware v.2.3.0.11291 allows a physically proximate attacker to execute arbitrary code via the factory test feature.","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":"Security feature bypass in n/a","id":"CVE-2026-36933","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2026-36937"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2026-36923"},"products":["n/a"],"published":"2026-06-15","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-16","vendors":["n/a"]},"summary":"A physically proximate attacker can execute arbitrary code on Boyleep K11 and y108 smartwatches by exploiting the factory test feature.","url":"https://insights.sbomify.com/CVE-2026-36933/"}