{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-49241 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-49241 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49241 is a high-severity code injection vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-49241 and fix it if it is affected.\n\nWhat it is: CVE-2026-49241 is a high-severity code injection vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-49241 in the wild and no public exploit code.\n\nAffected product: angular. 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-49241/ (Markdown: https://insights.sbomify.com/CVE-2026-49241/index.md)","id":"CVE-2026-49241","markdown":"https://insights.sbomify.com/CVE-2026-49241/index.md","name":"CVE-2026-49241","record":{"aliases":["GHSA-ccq4-xmxr-8hcq","UBUNTU-CVE-2026-49241"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"VS Code extension","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking developers into opening a malicious repository that loads a crafted TypeScript SDK via the Angular Language Service extension.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"angular_language_service","vendor":"angular"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-494","name":"Download of Code Without Integrity Check"},{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"The Angular Language Service VS Code Extension provides a rich editing experience for Angular templates. Prior to 21.2.4, the client-side Angular Language Service VS Code extension reads the custom TypeScript SDK paths typescript.tsdk and js/ts.tsdk.path directly from workspace configurations (.vscode/settings.json) without verifying VS Code Workspace Trust state or asking for user consent (located in client/src/client.ts). The client-side extension then passes the parsed settings path as a command-line argument (--tsdk) to the background Node.js language server process. During server initialization, the background language server resolves and dynamically imports (via standard Node.js require()) the module library tsserverlibrary.js relative to the workspace-specified custom directory path. An attacker can exploit this behavior by committing a repository containing a local malicious tsserverlibrary.js script inside a custom folder, and a crafted .vscode/settings.json file pointing to that folder. When a developer opens the repository folder in VS Code, the extension automatically attempts to initialize and load the server, which dynamically resolves, loads, and executes the malicious script silently in the background. This vulnerability is fixed in 21.2.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Angular: Multiple Remote Code Execution Vulnerabilities in Angular Language Service VS Code Extension","id":"CVE-2026-49241","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Webmin: Reflected XSS in the Configuration module","id":"CVE-2026-49243"},"packages":[],"prev":{"headline":"SFTP Server VM Escape in Canonical Multipass","id":"CVE-2026-49238"},"products":["angular"],"published":"2026-06-22","related":[{"cvss_score":8.7,"headline":"Angular: Remote Code Execution via JSDoc Hover Command Injection in VS Code Angular Language Service Extension","id":"CVE-2026-50178","kev_date_added":null,"published":"2026-06-22"}],"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":"total"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["angular"]},"summary":"Attackers can execute arbitrary code by tricking developers into opening a malicious repository that loads a crafted TypeScript SDK via the Angular Language Service extension.","url":"https://insights.sbomify.com/CVE-2026-49241/"}