CVE-2026-47287
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRelative path traversal in Visual Studio Code allows an unauthorized attacker to perform tampering over a network.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceRelative path traversal in Visual Studio Code allows attackers to use path manipulation sequences (such as ../) to access files and directories outside the intended restricted area, enabling unauthorized file tampering over a network.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.0.0, < 1.123.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check VS Code version via command lineOpen a terminal and run: code --versionAffected if The version output is 1.0.0 or higher but lower than 1.123.1
-
Check VS Code version via UIIn VS Code, go to Help > About. The version number is displayed in the dialog that opens.Affected if The displayed version is 1.0.0 or higher but lower than 1.123.1
-
Verify version number formatEnsure you are checking the main version number (e.g., 1.123.0), not a pre-release or insiders build version. Compare against the vulnerable range: >= 1.0.0 and < 1.123.1Affected if The installed version falls within the vulnerable range
You are affected if your installed Visual Studio Code version is 1.0.0 or higher but less than 1.123.1, since the path traversal vulnerability exists in all versions within this range.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.123.1
Implement strict input validation and canonicalization of file paths before use, ensuring paths resolve within expected boundaries and rejecting any traversal sequences.
Visual Studio Code 1.123.1 or later
- Open Visual Studio Code
- Navigate to the Help menu (or use the command palette)
- Check for updates via 'Help > Check for Updates' or run the 'Update: Check for Update' command
- Allow VS Code to download and install version 1.123.1 or later
- Restart Visual Studio Code to complete the update
- Alternatively, download Visual Studio Code 1.123.1 or later directly from the official website (code.visualstudio.com)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47287 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data