Vulnerability in baseline-browser-mapping (CVE-2026-45819)
Summary
Vulnerability in baseline-browser-mapping (CVE-2026-45819). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.11.0 or later.
Original description
The description as published by the source.
baseline-browser-mapping 2.x before 2.11.0 calls process.exit() instead of throwing on invalid or conflicting input parameters, and can trigger immediate process termination, causing denial of service.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45819 has been found in baseline-browser-mapping.
Risk of unauthorized operations or information disclosure.
What to do: upgrade baseline-browser-mapping to 2.11.0 or later.
If unsure, ask your IT team or search "baseline-browser-mapping CVE-2026-45819" on the vendor's site.
CVE-2026-45819 (baseline-browser-mapping) — CWE-705
Patched: 2.11.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-705) exists in baseline-browser-mapping.
Check the vendor advisory for the affected versions of baseline-browser-mapping.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.11.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'baseline-browser-mapping' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'baseline-browser-mapping' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
baseline-browser-mappingを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade baseline-browser-mapping to 2.11.0ステージング環境で 2.11.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web npmjs.com
- web github.com
- web github.com
- web github.com
- web github.com