{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119818 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119818 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119818 is a high-severity vulnerability in Microsoft Windows 10 Version 1607, published on 10 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-119818 and fix it if it is affected.\n\nWhat it is: CVE-2026-119818 is a high-severity vulnerability in Microsoft Windows 10 Version 1607, published on 10 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-119818 in the wild and no public exploit code.\n\nAffected product: Microsoft Windows 10 Version 1607. 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-119818/ (Markdown: https://insights.sbomify.com/CVE-2026-119818/index.md)","id":"CVE-2026-119818","markdown":"https://insights.sbomify.com/CVE-2026-119818/index.md","name":"CVE-2026-119818","record":{"aliases":["GHSA-xv7g-c9xq-3c3m"],"analysis":null,"analysis_generated_by":null,"assigner":"microsoft","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Incorrect authorization in Windows Text Services Framework allows an authorized attacker to elevate privileges locally.","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":"Windows Text Services Framework Elevation of Privilege Vulnerability","id":"CVE-2026-119818","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Windows Network Connection Broker Elevation of Privilege Vulnerability","id":"CVE-2026-119821"},"nickname":null,"packages":[],"prev":{"headline":"Windows Shell Elevation of Privilege Vulnerability","id":"CVE-2026-119817"},"products":["Windows 10 Version 1607","Windows 10 Version 1809","Windows 10 Version 21H2","Windows 10 Version 22H2","Windows 11 Version 23H2","Windows 11 Version 24H2","Windows 11 Version 25H2","Windows 11 Version 26H2","Windows 11 version 23H2","Windows 11 version 26H1","Windows Server 2016","Windows Server 2016 (Server Core installation)","Windows Server 2019","Windows Server 2019 (Server Core installation)","Windows Server 2022","Windows Server 2025","Windows Server 2025 (Server Core installation)"],"published":"2026-11-10","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":"total"},"state":"PUBLISHED","updated":"2026-11-12","vendors":["Microsoft"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119818/"}