{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-49483 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-49483 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49483 is a high-severity vulnerability in codefori vscode-ibmi, published on 12 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-49483 and fix it if it is affected.\n\nWhat it is: CVE-2026-49483 is a high-severity vulnerability in codefori vscode-ibmi, published on 12 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-49483 in the wild and no public exploit code.\n\nAffected product: codefori vscode-ibmi. 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-49483/ (Markdown: https://insights.sbomify.com/CVE-2026-49483/index.md)","id":"CVE-2026-49483","markdown":"https://insights.sbomify.com/CVE-2026-49483/index.md","name":"CVE-2026-49483","record":{"aliases":["GHSA-rmqv-7c5v-wvjc"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"VS Code extension","requires_auth":"low_privilege","summary":"A local attacker can modify IBM i components to execute arbitrary code under the connecting user's account due to insufficient integrity checks.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.9,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Code for IBMi is a Visual Studio Code extension for maintaining and compiling ILE languages on the IBMi platform. Prior to 3.0.1, IBMi components implementing IBMiComponent were accepted after checking that a procedure existed without reliably verifying component integrity. Components installed with broad public permissions allow another local account to alter a program such as GETMBRINFO. A later connection can execute the altered program under the connecting account because the LONG_COMMENT marker alone does not establish integrity. This issue is fixed in version 3.0.1.","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":"Code for IBMi: Uses IBM i components with blind check allowing arbitrary code execution","id":"CVE-2026-49483","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Code for IBM i: Temporary files are visible to all users","id":"CVE-2026-49484"},"packages":[],"prev":{"headline":"ClipBucket: SQL Wildcard Injection in Subtitle Edit Endpoint Allows Mass Subtitle Overwrite","id":"CVE-2026-49482"},"products":["vscode-ibmi"],"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":"total"},"state":"PUBLISHED","updated":"2026-10-13","vendors":["codefori"]},"summary":"A local attacker can modify IBM i components to execute arbitrary code under the connecting user's account due to insufficient integrity checks.","url":"https://insights.sbomify.com/CVE-2026-49483/"}