{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-41977 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-41977 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41977 is a medium-severity vulnerability in Huawei EMUI, published on 9 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-41977 and fix it if it is affected.\n\nWhat it is: CVE-2026-41977 is a medium-severity vulnerability in Huawei EMUI, published on 9 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-41977 in the wild and no public exploit code.\n\nAffected product: Huawei EMUI. 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-41977/ (Markdown: https://insights.sbomify.com/CVE-2026-41977/index.md)","id":"CVE-2026-41977","markdown":"https://insights.sbomify.com/CVE-2026-41977/index.md","name":"CVE-2026-41977","record":{"aliases":["GHSA-988p-jh3p-gxwh"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei mobile OS","requires_auth":"none","summary":"An integer overflow in the log service allows attackers to cause a denial of service on Huawei mobile devices.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"DoS vulnerability in the log service. 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":"Integer overflow in EMUI","id":"CVE-2026-41977","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in HarmonyOS","id":"CVE-2026-41978"},"packages":[],"prev":{"headline":"Missing authorization in EMUI","id":"CVE-2026-41976"},"products":["EMUI","HarmonyOS"],"published":"2026-06-09","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-06-09","vendors":["Huawei"]},"summary":"An integer overflow in the log service allows attackers to cause a denial of service on Huawei mobile devices.","url":"https://insights.sbomify.com/CVE-2026-41977/"}