Read the docs
TI-2021-05504 Aliases CVE-2021-22539

Code execution in VSCode-bazel via malicious Bazel config files

Priority LOW 35CWE-73Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
Required
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

An attacker can place a crafted JSON config file into the project folder pointing to a custom executable. VScode-bazel allows the workspace path to lint *.bzl files to be set via this config file. As such the attacker is able to execute any executable on the system through vscode-bazel. We recommend upgrading to version 0.4.1 or above.

Why it matters now

EPSS 0.0031 24th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
GoogleVSCode-Bazelup to 0.4.0—No fix listedCNA
  • VSCode-Bazel VendorGoogle Affected up to 0.4.0 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:google:bazel:*:*:*:*:*:visual_studio:*:*0.1.0 to before 0.4.1VulnerableGoogle
  • cpe:2.3:a:google:bazel:*:*:*:*:*:visual_studio:*:* Versions 0.1.0 to before 0.4.1 Vulnerable ·Google

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2021-22539

References

Advisory 1

Other 1

  • TI-2022-03208 Bazel leaks user credentials through the remote assets API CVSS 4.0MEDIUM 5.1

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences