{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89038 exists.","fix":"No fix has been published for CVE-2026-89038 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-89038 is a medium-severity path traversal vulnerability in Verizon Cloud for Android, published on 17 Sep 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-89038 and fix it if it is affected.\n\nWhat it is: CVE-2026-89038 is a medium-severity path traversal vulnerability in Verizon Cloud for Android, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89038 exists.\n\nAffected product: Verizon Cloud for Android. 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-89038/ (Markdown: https://insights.sbomify.com/CVE-2026-89038/index.md)","id":"CVE-2026-89038","markdown":"https://insights.sbomify.com/CVE-2026-89038/index.md","name":"CVE-2026-89038","record":{"aliases":["GHSA-x3gc-cx3q-fw5m"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Verizon Cloud Android app","requires_auth":"none","summary":"Malicious apps can write arbitrary files to the user's Verizon Cloud account via path traversal in exported activities, potentially injecting content without user interaction.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Verizon Cloud for Android (com.vcast.mediamanager) before 26.7.10 contains a path traversal vulnerability that allows co-resident malicious applications to write attacker-controlled bytes outside the intended staging directory by supplying a crafted _display_name value containing path-traversal sequences through exported activities OneTouchUploadActivity and PrintShopCloudActivity. Attackers can exploit the unsanitized filename concatenation in the file-staging sink via ACTION_SEND or ACTION_SEND_MULTIPLE intents to achieve arbitrary file write and inject attacker-controlled content into the authenticated user's Verizon Cloud account without user interaction.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Verizon Cloud for Android \u003c 26.7.10 Path Traversal via OneTouchUploadActivity","id":"CVE-2026-89038","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Arbitrary file read via the convert_playwright_script prompt in mcp-k6","id":"CVE-2026-89039"},"packages":[],"prev":{"headline":"Appwrite \u003c 2.0.0 Argument Injection via providerRootDirectory Parameter","id":"CVE-2026-89036"},"products":["Verizon Cloud for Android"],"published":"2026-09-17","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["Verizon"]},"summary":"Malicious apps can write arbitrary files to the user's Verizon Cloud account via path traversal in exported activities, potentially injecting content without user interaction.","url":"https://insights.sbomify.com/CVE-2026-89038/"}