{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42447 exists.","fix":"No fix has been published for CVE-2026-42447 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42447 is a low-severity cross-site scripting vulnerability in skylot jadx, published on 14 Jul 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-42447 and fix it if it is affected.\n\nWhat it is: CVE-2026-42447 is a low-severity cross-site scripting vulnerability in skylot jadx, published on 14 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42447 exists.\n\nAffected product: skylot jadx. 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-42447/ (Markdown: https://insights.sbomify.com/CVE-2026-42447/index.md)","id":"CVE-2026-42447","markdown":"https://insights.sbomify.com/CVE-2026-42447/index.md","name":"CVE-2026-42447","record":{"aliases":["GHSA-jwv3-q635-w9m4"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java decompiler GUI","requires_auth":"none","summary":"Attackers can inject HTML into jadx-gui via malicious APKs, enabling IP disclosure or local application interaction.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jadx","vendor":"jadx_project"}],"cvss":{"score":3.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"jadx is a Dex to Java decompiler. Prior to 1.5.6, jadx-gui is affected by an HTML injection vulnerability in the Summary tab because SummaryNode.java appends arches and perArchCount values derived from .so file path components inside an APK into an HTML panel without escaping. A malicious APK with an HTML URL-encoded ZIP entry name can force rendering of arbitrary HTML, perform out-of-band requests, disclose the victim IP address, or interact with locally exposed applications. This issue is fixed in version 1.5.6.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"jadx: HTML Injection in Summary panel","id":"CVE-2026-42447","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"wormhole receive, with --output pointing at an existing directory can be path-traversed","id":"CVE-2026-42448"},"packages":[],"prev":{"headline":"NanaZip: Stack out-of-bounds read in NanaZip ZealFS bitmap parser","id":"CVE-2026-42446"},"products":["jadx"],"published":"2026-07-14","related":[{"cvss_score":5.5,"headline":"Improper Restriction of XML External Entity Reference in skylot/jadx","id":"CVE-2022-0219","kev_date_added":null,"published":"2022-01-20"},{"cvss_score":3.3,"headline":"Jadx-gui subject to Denial of Service via Swing HTML rendering","id":"CVE-2022-39259","kev_date_added":null,"published":"2022-10-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["skylot"]},"summary":"Attackers can inject HTML into jadx-gui via malicious APKs, enabling IP disclosure or local application interaction.","url":"https://insights.sbomify.com/CVE-2026-42447/"}