{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-41967 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-41967 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41967 is a medium-severity missing authorization vulnerability in Huawei HarmonyOS, published on 15 May 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-41967 and fix it if it is affected.\n\nWhat it is: CVE-2026-41967 is a medium-severity missing authorization vulnerability in Huawei HarmonyOS, published on 15 May 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-41967 in the wild and no public exploit code.\n\nAffected product: Huawei HarmonyOS. 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-41967/ (Markdown: https://insights.sbomify.com/CVE-2026-41967/index.md)","id":"CVE-2026-41967","markdown":"https://insights.sbomify.com/CVE-2026-41967/index.md","name":"CVE-2026-41967","record":{"aliases":["GHSA-mmcj-637g-3xw4"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HarmonyOS","requires_auth":"none","summary":"Attackers can exploit permission control flaws in the manufacturability design module to disrupt system availability.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-840","name":null}],"description":"Permission control vulnerability in the manufacturability design module. Impact: Successful exploitation of this vulnerability may affect availability.","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":"Missing authorization in HarmonyOS","id":"CVE-2026-41967","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in HarmonyOS","id":"CVE-2026-41968"},"packages":[],"prev":{"headline":"Missing authorization in HarmonyOS","id":"CVE-2026-41966"},"products":["HarmonyOS"],"published":"2026-05-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":"partial"},"state":"PUBLISHED","updated":"2026-05-15","vendors":["Huawei"]},"summary":"Attackers can exploit permission control flaws in the manufacturability design module to disrupt system availability.","url":"https://insights.sbomify.com/CVE-2026-41967/"}