# CVE-2026-49484: Code for IBM i: Temporary files are visible to all users

> Local attackers can read sensitive files stored in the shared /tmp directory by the Code for IBM i extension during download or edit operations.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-9869-gm55-mqpq

## What is CVE-2026-49484?

CVE-2026-49484 is a medium-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.

### Official description

Code for IBM i is a Visual Studio Code extension for maintaining and compiling ILE languages on the IBMi platform. Prior to 3.0.1, src/ui/views/objectBrowser.ts stores Object Browser downloads and the edit-save flow content in the shared /tmp directory without reliable cleanup. On systems where /tmp is accessible to other local accounts, file contents remain readable after download or editing operations. This issue is fixed in version 3.0.1.

Weakness: CWE-459 (Incomplete Cleanup), CWE-377 (DEPRECATED: Insecure Temporary File)

## Which versions are affected by CVE-2026-49484?


## How do I fix CVE-2026-49484?

No fix has been published for CVE-2026-49484 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49484 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49484 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49484 and fix it if it is affected.

What it is: CVE-2026-49484 is a medium-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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49484 exists.

Affected product: codefori vscode-ibmi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49484/ (Markdown: https://insights.sbomify.com/CVE-2026-49484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49484
- OSV: https://osv.dev/vulnerability/CVE-2026-49484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49484/
Summaries are generated and may contain mistakes; the official description above is the record.