{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-21133 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-21133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21133 is a medium-severity path traversal vulnerability in Samsung Flow, published on 12 Oct 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-21133 and fix it if it is affected.\n\nWhat it is: CVE-2026-21133 is a medium-severity path traversal vulnerability in Samsung Flow, published on 12 Oct 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-21133 in the wild and no public exploit code.\n\nAffected product: Samsung Flow. 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-21133/ (Markdown: https://insights.sbomify.com/CVE-2026-21133/index.md)","id":"CVE-2026-21133","markdown":"https://insights.sbomify.com/CVE-2026-21133/index.md","name":"CVE-2026-21133","record":{"aliases":["GHSA-4gxh-659v-jqg2"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Flow app","requires_auth":"none","summary":"Local attackers can exploit a path traversal flaw in Samsung Flow to access sensitive clipboard data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/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":"Path traversal in Samsung Flow prior to version 4.9.22.1 allows local attackers to access clipboard data.","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":"Path traversal in Samsung Flow","id":"CVE-2026-21133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in Samsung Flow","id":"CVE-2026-21134"},"packages":[],"prev":{"headline":"Cross-site scripting in Samsung Internet","id":"CVE-2026-21132"},"products":["Samsung Flow"],"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-16","vendors":["Samsung Mobile"]},"summary":"Local attackers can exploit a path traversal flaw in Samsung Flow to access sensitive clipboard data.","url":"https://insights.sbomify.com/CVE-2026-21133/"}