CVE-2026-45819 — baseline-browser-mapping
Fix: web-platform-dx/baseline-browser-mapping#137CVE-2026-45819 is a CWE-705 vulnerability in baseline-browser-mapping. A fix is available for baseline-browser-mapping — see the affected versions and patch details below.
baseline-browser-mapping process termination on invalid input causes denial of service
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-45819.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
baseline-browser-mappingnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | baseline-browser-mapping | ≥ 2.0.0&&< 2.11.0 | 2.11.0npm install baseline-browser-mapping@2.11.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for baseline-browser-mapping, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update baseline-browser-mapping to 2.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-45819 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-45819 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-45819. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Important: This flaw in the 'baseline-browser-mapping' library can result in a denial of service. Applications utilizing this library may unexpectedly terminate if they process invalid or conflicting input parameters, potentially disrupting services.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Hardened Images | grafana13-1-main-13.1.3-0.1.1.hum1 | RHSA-2026:54517 |
| Red Hat Hardened Images | grafana12-4-main-12.4.8-0.1.1.hum1 | RHSA-2026:54518 |
| Red Hat OpenShift AI 2.25 | rhoai/odh-dashboard-rhel9:1788312226 | RHSA-2026:65126 |
Frequently Asked Questions
Is CVE-2026-45819 in your dependencies?
O3 Security finds CVE-2026-45819 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.