{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-109424 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-109424 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-109424 is a high-severity vulnerability in NetEase Cloud Music for Windows, published on 12 Oct 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-109424 and fix it if it is affected.\n\nWhat it is: CVE-2026-109424 is a high-severity vulnerability in NetEase Cloud Music for Windows, published on 12 Oct 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-109424 in the wild and no public exploit code.\n\nAffected product: NetEase Cloud Music for Windows. 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-109424/ (Markdown: https://insights.sbomify.com/CVE-2026-109424/index.md)","id":"CVE-2026-109424","markdown":"https://insights.sbomify.com/CVE-2026-109424/index.md","name":"CVE-2026-109424","record":{"aliases":["GHSA-h7w7-mfj4-5gxw"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"NetEase Cloud Music","requires_auth":"none","summary":"Attackers can forge API responses using a hardcoded AES key, enabling data interception and potential code execution via navigation bridges.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"NetEase Cloud Music client for Windows (cloudmusic.exe) versions 3.1.38 and 3.1.39.205426 contains a weak encryption vulnerability where /eapi/ and /xeapi/ API response bodies are decrypted using a fixed, publicly documented AES-128-ECB key with no integrity credential. Attackers who can intercept or originate server responses can construct valid ciphertext under the known key with PKCS#7 padding, enabling the client to accept forged API responses that serve as a prerequisite for further exploitation such as reaching the os.navigateExternal bridge.","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":"NetEase Cloud Music Weak Encryption via eapi/xeapi","id":"CVE-2026-109424","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Tink-go 2.8.0 Keyset Validation Bypass via NewHandleWithNoSecrets","id":"CVE-2026-109425"},"packages":[],"prev":{"headline":"NetEase Cloud Music TLS Certificate Validation Bypass","id":"CVE-2026-109423"},"products":["NetEase Cloud Music for Windows"],"published":"2026-10-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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-13","vendors":["NetEase"]},"summary":"Attackers can forge API responses using a hardcoded AES key, enabling data interception and potential code execution via navigation bridges.","url":"https://insights.sbomify.com/CVE-2026-109424/"}