High [CVE-2026-45819] Denial of Service via improper input handling
This high-severity Red Hat Linux advisory covers CVE-2026-45819 affecting Cryostat 4, OpenShift Lightspeed, OpenShift Pipelines.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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. The affected component improperly terminates the process instead of handling the input error gracefully, leading to immediate service disruption.
Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-617.
Affected Red Hat products: Cryostat 4; OpenShift Lightspeed; OpenShift Pipelines; OpenShift Service Mesh 3; Red Hat AMQ Broker 7; Red Hat Ansible Automation Platform 2; Red Hat Build of Keycloak; Red Hat Build of Podman Desktop; Red Hat Ceph Storage 9; Red Hat Data Grid 8; Red Hat Discovery 2; Red Hat Edge Manager 1; Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9; Red Hat Enterprise Linux AI (RHEL AI) 3; Red Hat Hardened Images; Red Hat OpenShift AI (RHOAI); Red Hat OpenShift Container Platform 4; Red Hat Openshift Data Foundation 4; Red Hat OpenShift Dev Spaces; Red Hat Quay 3; Red Hat Satellite 6; Secrets Management Console for Red Hat OpenShift; Self-service automation portal 2.
Red Hat lists Red Hat Developer Hub; Red Hat Enterprise Linux 8 as not affected. Will not fix / out of support: Secrets Management Console for Red Hat OpenShift.
Red Hat does not currently list a fixing RHSA for this CVE.
- < 2.11.0
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.