Skip to content

chore: upgrade baseline-browser-mapping to 2.11.21 to address CVE-2026-45819 - #1645

Open
claude[bot] wants to merge 2 commits into
mainfrom
cursor/cve/baseline-browser-mapping
Open

chore: upgrade baseline-browser-mapping to 2.11.21 to address CVE-2026-45819#1645
claude[bot] wants to merge 2 commits into
mainfrom
cursor/cve/baseline-browser-mapping

Conversation

@claude

@claude claude Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Fixes SOU-2202

Refreshes the yarn.lock entries for baseline-browser-mapping, which now dedupe onto 2.11.21.

baseline-browser-mapping is not a direct dependency of any workspace. It arrived twice: through browserslist at ^2.11.12 (already resolving to a patched 2.11.20) and through next at ^2.9.19, which was stale at the affected 2.10.13. Both ranges already admitted the patched release, so this is a lockfile refresh only. No package.json change and no resolutions override were needed.

Advisory addressed

Advisory Patched in Summary
CVE-2026-45819 2.11.0 Calls process.exit() instead of throwing on invalid or conflicting input parameters, allowing immediate process termination

Verification

  • yarn why baseline-browser-mapping reports every instance resolving to baseline-browser-mapping@npm:2.11.21, with 2.10.13 gone from the graph.
  • yarn workspace @sourcebot/web test --run — 140 files, 1440 tests passed.
  • yarn workspace @sourcebot/web build — succeeded. Included because this package feeds browserslist target resolution at build time.

🤖 Generated with Claude Code


Note

Low Risk
Lockfile-only transitive dependency bump for a security advisory; no application code or direct dependency version changes.

Overview
Refreshes yarn.lock so every transitive baseline-browser-mapping instance resolves to 2.11.21, removing the stale 2.10.13 copy that came in through next while browserslist was already on a newer line.

There are no package.json or resolutions changes—existing semver ranges already allowed the patched release. The [Unreleased] changelog records the upgrade under Fixed.

This addresses CVE-2026-45819, where invalid or conflicting CLI input could trigger process.exit() instead of a thrown error and terminate the Node process.

Reviewed by Cursor Bugbot for commit e1069a4. Bugbot is set up for automated code reviews on this repo. Configure here.


Summary by cubic

Fixes SOU-2202 by upgrading baseline-browser-mapping to 2.11.21 in yarn.lock, addressing CVE-2026-45819. This is a lockfile-only refresh; both browserslist and next already permitted the patched version.

  • yarn why confirms all instances resolve to 2.11.21.
  • Workspace tests and build pass.

Written for commit b088139. Summary will update on new commits.

Review in cubic

github-actions Bot and others added 2 commits September 10, 2026 12:42
Refreshes the yarn.lock entries for baseline-browser-mapping. next
requested it at `^2.9.19`, which was stale at 2.10.13; that range already
admitted the patched version, so no manifest change or resolution override
is needed. The two lock entries now dedupe onto 2.11.21.

Addresses CVE-2026-45819.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

@claude[bot] your pull request is missing a changelog!

@claude
claude Bot requested a review from brendan-kellam September 10, 2026 12:42
@github-actions

Copy link
Copy Markdown
Contributor

License Audit

❌ Audit failed to produce results. Check the workflow logs for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants