CVE-2026-45819

MEDIUMPre-NVD 6.66.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.6
EG Score
6.6MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity66% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
Patch available. Sources: github_pr.
github_pr Patch Available

feat: add getTimeline() and refactor data compression

Patch available: web-platform-dx/baseline-browser-mapping v2.11.0 (PR #137 merged 2026-07-21)

https://github.com/web-platform-dx/baseline-browser-mapping/pull/137/changes#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519
generic

baseline-browser-mapping/src/index.ts at b7881aa61c8a057e24468ab5ee18c5ecedbbf691 · web-platform-dx/baseline-browser-mapping · GitHub

https://github.com/web-platform-dx/baseline-browser-mapping/blob/b7881aa61c8a057e24468ab5ee18c5ecedbbf691/src/index.ts#L142

Vendor Advisories for CVE-2026-45819(14)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-agent-installer-ui-rhel9:17901308742026-09-29redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17895928062026-09-22redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17895678492026-09-22redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17896609692026-09-17redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17896609832026-09-17redhat
redhatdevspaces/dashboard-rhel9:17891628842026-09-17redhat
redhatrhem/flightctl-ui-rhel10:17894881112026-09-16redhat
redhatrhem/flightctl-ui-rhel10:17894861812026-09-16redhat
redhatrhem/flightctl-ui-ocp-rhel9:17894864462026-09-16redhat
redhatrhem/flightctl-ui-rhel9:17894867502026-09-16redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17883121572026-09-08redhat
redhatgrafana13-1-main-13.1.3-0.1.1.hum12026-08-13redhat
redhatgrafana12-4-main-12.4.8-0.1.1.hum12026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
baseline-browser-mapping—
  • 2.0.0 up to 2.11.0: fixed in 2.11.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 172 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-06 13:57 UTCEG score recompute
  6. 2026-10-06 13:57 UTCVendor advisory
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-04 23:22 UTCEPSS rescore
  9. 2026-10-04 22:25 UTCVendor advisory
  10. 2026-10-03 19:53 UTCEG score recompute
  11. 2026-10-03 19:53 UTCVendor advisory
  12. 2026-10-03 14:25 UTCEPSS rescore
  13. 2026-10-02 08:06 UTCEG score recompute
  14. 2026-10-02 08:06 UTCVendor advisory
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-09-30 21:51 UTCEG score recompute
  17. 2026-09-30 21:51 UTCVendor advisory
  18. 2026-09-30 15:03 UTCEPSS rescore
  19. 2026-09-29 08:19 UTCEG score recompute
  20. 2026-09-29 08:19 UTCVendor advisory
  21. 2026-09-28 08:55 UTCEG score recompute
  22. 2026-09-28 08:55 UTCVendor advisory
  23. 2026-09-27 13:48 UTCEPSS rescore
  24. 2026-09-27 09:49 UTCEG score recompute
  25. 2026-09-27 09:49 UTCVendor advisory
Show 75 more
  1. 2026-09-26 15:58 UTCEPSS rescore
  2. 2026-09-25 07:15 UTCEG score recompute
  3. 2026-09-25 07:15 UTCVendor advisory
  4. 2026-09-24 08:09 UTCEG score recompute
  5. 2026-09-24 08:09 UTCVendor advisory
  6. 2026-09-23 17:53 UTCEPSS rescore
  7. 2026-09-23 09:03 UTCEG score recompute
  8. 2026-09-23 09:03 UTCVendor advisory
  9. 2026-09-22 09:57 UTCEG score recompute
  10. 2026-09-22 09:57 UTCVendor advisory
  11. 2026-09-21 09:43 UTCEG score recompute
  12. 2026-09-21 09:43 UTCVendor advisory
  13. 2026-09-20 20:15 UTCEPSS rescore
  14. 2026-09-20 10:21 UTCEG score recompute
  15. 2026-09-20 10:21 UTCVendor advisory
  16. 2026-09-19 11:16 UTCEG score recompute
  17. 2026-09-19 11:16 UTCVendor advisory
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 11:21 UTCEG score recompute
  20. 2026-09-18 11:21 UTCVendor advisory
  21. 2026-09-17 19:31 UTCEPSS rescore
  22. 2026-09-17 12:14 UTCEG score recompute
  23. 2026-09-17 12:14 UTCVendor advisory
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 12:12 UTCEG score recompute
  26. 2026-09-16 12:12 UTCVendor advisory
  27. 2026-09-16 05:15 UTCEPSS rescore
  28. 2026-09-15 13:06 UTCEG score recompute
  29. 2026-09-15 13:06 UTCVendor advisory
  30. 2026-09-14 12:14 UTCEG score recompute
  31. 2026-09-14 12:14 UTCVendor advisory
  32. 2026-09-13 16:47 UTCEPSS rescore
  33. 2026-09-13 13:08 UTCEG score recompute
  34. 2026-09-13 13:08 UTCVendor advisory
  35. 2026-09-12 15:01 UTCEPSS rescore
  36. 2026-09-12 14:02 UTCVendor advisory
  37. 2026-09-11 14:55 UTCEG score recompute
  38. 2026-09-11 14:55 UTCVendor advisory
  39. 2026-09-11 14:53 UTCEPSS rescore
  40. 2026-09-11 09:37 UTCEPSS rescore
  41. 2026-09-10 15:49 UTCEG score recompute
  42. 2026-09-10 15:49 UTCVendor advisory
  43. 2026-09-10 09:34 UTCEPSS rescore
  44. 2026-09-09 16:14 UTCVendor advisory
  45. 2026-09-09 05:07 UTCEG score recompute
  46. 2026-09-09 05:07 UTCVendor advisory
  47. 2026-09-08 22:00 UTCEPSS rescore
  48. 2026-09-08 00:31 UTCEG score recompute
  49. 2026-09-08 00:31 UTCVendor advisory
  50. 2026-09-08 00:31 UTCGHSA enrichment
  51. 2026-09-07 16:01 UTCEPSS rescore
  52. 2026-09-07 01:24 UTCEG score recompute
  53. 2026-09-07 01:24 UTCVendor advisory
  54. 2026-09-07 01:24 UTCGHSA enrichment
  55. 2026-09-06 13:47 UTCEPSS rescore
  56. 2026-09-06 02:18 UTCEG score recompute
  57. 2026-09-06 02:18 UTCVendor advisory
  58. 2026-09-06 02:18 UTCGHSA enrichment
  59. 2026-09-05 03:12 UTCEG score recompute
  60. 2026-09-05 03:12 UTCVendor advisory
  61. 2026-09-05 03:12 UTCGHSA enrichment
  62. 2026-09-04 05:06 UTCEPSS rescore
  63. 2026-09-04 03:43 UTCVendor advisory
  64. 2026-09-04 03:42 UTCGHSA enrichment
  65. 2026-09-03 04:35 UTCEG score recompute
  66. 2026-09-03 04:35 UTCVendor advisory
  67. 2026-09-03 04:35 UTCGHSA enrichment
  68. 2026-09-02 14:12 UTCEPSS rescore
  69. 2026-09-02 05:25 UTCEG score recompute
  70. 2026-09-02 05:25 UTCVendor advisory
  71. 2026-09-02 05:25 UTCGHSA enrichment
  72. 2026-09-01 13:54 UTCEPSS rescore
  73. 2026-09-01 06:19 UTCEG score recompute
  74. 2026-09-01 06:19 UTCVendor advisory
  75. 2026-09-01 06:18 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45819?
CVE-2026-45819 is a medium vulnerability published on August 13, 2026. 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.
When was CVE-2026-45819 disclosed?
CVE-2026-45819 was first published on August 13, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45819 actively exploited?
CVE-2026-45819 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45819?
CVE-2026-45819 has a CVSS base score of 6.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45819?
A fix for CVE-2026-45819 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45819 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45819

Explore →

Is Your Infrastructure Affected by CVE-2026-45819?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs