{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46571 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-46571 is a medium-severity vulnerability in n/a, published on 7 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-46571 and fix it if it is affected.\n\nWhat it is: CVE-2026-46571 is a medium-severity vulnerability in n/a, published on 7 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-46571 in the wild and no public exploit code.\n\nAffected product: n/a. 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-46571/ (Markdown: https://insights.sbomify.com/CVE-2026-46571/index.md)","id":"CVE-2026-46571","markdown":"https://insights.sbomify.com/CVE-2026-46571/index.md","name":"CVE-2026-46571","record":{"aliases":["AZL-106878","DEBIAN-CVE-2026-46571","GHSA-52gr-j4pv-9pjh","UBUNTU-CVE-2026-46571"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NTFS filesystem driver","requires_auth":"low_privilege","summary":"An attacker can read confidential memory information by crafting a malicious NTFS image, affecting systems using NTFS-3G.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ntfs-3g","vendor":"tuxera"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In NTFS-3G before 2026.7.7, a out-of-bounds read exists in ntfs_fix_file_name() in libntfs-3g/reparse.c that allows an attacker to read possibly confidential information in ntfs-3g process memory by crafting a malicious NTFS image. The out-of-bounds read is triggered by a readlink on a corrupted file.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2026-46571","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2026-46572"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2026-46570"},"products":["n/a"],"published":"2026-10-07","related":[{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2026-46570","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2026-42616","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":7.7,"headline":"Memory corruption in n/a","id":"CVE-2026-46569","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":7.4,"headline":"Memory corruption in n/a","id":"CVE-2026-46572","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":7.4,"headline":"Memory corruption in n/a","id":"CVE-2026-56135","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2026-42617","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2026-42618","kev_date_added":null,"published":"2026-10-07"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["n/a"]},"summary":"An attacker can read confidential memory information by crafting a malicious NTFS image, affecting systems using NTFS-3G.","url":"https://insights.sbomify.com/CVE-2026-46571/"}