Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

vscodium/vscodium

              master @ eb5d6e2
            

Fixes

CVEs

HIGH

Peak severity

Highlights

Credential Exposure: 1 prior fix. Scrutinize any change in this area.

.github/workflows/stable-linux.yml: most-fixed (1 issue). Treat as high-risk during review.

1 high-severity fix in this history; regressions here are high-impact.

Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Sandbox Escape: Merging local configuration and invoking custom node-require logic in the renderer process historically allowed a sandbox escape. To prevent recurrence, all local product configuration and nodeRequire operations must be strictly resolved within the main process before sandboxing is initialized.

Credential Exposure: Improper syntax in GitHub Actions workflows resulted in failed token resolution and potential credential exposure when executing curl operations. Secrets must always be resolved via the formal github secrets context rather than raw environment variables.

Privilege Escalation: Default workflow run privileges can expose powerful GITHUB_TOKEN permissions. Workflows must adhere to the principle of least privilege by explicitly restricting the permissions block to empty in non-privileged check jobs.