A CVSS 7.8 score on a LOCAL attack vector should force a recalibration of how we contextualize risk. This vulnerability is dangerous not because it's remotely exploitable, but because it weaponizes a local foothold in an environment developers trust with high-value secrets — and that context changes everything.
The 'user-controlled key' mechanism in VS Code's architecture is the specific signal that demands attention. This phrasing almost certainly refers to settings keys, extension configuration parameters, or credential storage that the user has write access to. The vulnerability isn't that a local attacker can execute code on the workstation — it's that VS Code's security boundary treats user-writable configuration as data that can influence authorization decisions. That's not merely an architectural gap; it's a case of forgotten threat modeling where convenience features like settings sync and extension auto-update created paths that were never re-audited as the tool's trust boundaries evolved.
The critical insight: local access to a developer workstation doesn't stay local. VS Code is a trust hub — authenticated to GitHub and GitLab, connected to AWS/GCP/Azure CLIs, accessing private registries, maintaining persistent OAuth sessions. A local authorization bypass here doesn't compromise a single system; it compromises the node that every other system expects to be trustworthy. CVSS measures impact on the immediately affected component; it doesn't model what happens when the compromised component is the credential store authenticating to everything else.
Compounding this: developer workstations are patched last. The LOCAL qualifier functions as a deprioritization signal in most organizations — this gets triaged below remote RCEs. The exposure window isn't just time to patch, it's the compounded delay across every organization that treats 'local' as 'low urgency.' A 7.8 score doesn't model this systematic remediation lag.
Check your VS Code installation for unauthorized extension installations, unexpected settings modifications in your sync profile, and any new authentication tokens appearing in your keyring or credential manager. Treat any local compromise of a developer workstation as a full credential rotation event — because that's exactly what it is.