Medium [CVE-2026-48928] Trust-policy bypass due to hostname matching inconsistency
This medium-severity Red Hat Linux advisory covers CVE-2026-48928 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
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
A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
A flaw was found in Node.js. An inconsistency in how Node.js matches hostnames can be exploited by a remote attacker in multi-context mTLS (mutual Transport Layer Security) setups.
This vulnerability allows for a trust-policy bypass, potentially leading to unauthorized access to sensitive information or integrity compromise within the affected system. Red Hat severity: Moderate — CVSS 4.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N).
Weakness: CWE-289. Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Hardened Images.
Red Hat fixing advisory: RHSA-2026:35841, RHSA-2026:35842, RHSA-2026:39868, RHSA-2026:41947, RHSA-2026:35891, RHSA-2026:35892, RHSA-2026:33866, RHSA-2026:34478, RHSA-2026:35272, RHSA-2026:7378, RHSA-2026:9455.
Affected products named by the advisory: Red Hat package: nodejs24; Red Hat package: nodejs22.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- nodejs24-1:24.18.0-1.el10_2
- nodejs22-1:22.23.1-2.el10_2
- nodejs:24-8100020260630152626.6d880403
- nodejs:22-8100020260703140402.6d880403
- nodejs:24-9080020260626074955.rhel9
- nodejs:22-9080020260626075442.rhel9
- nodejs26-main-26.4.0-1.3.hum1
- nodejs24-main-24.18.0-0.2.hum1
- nodejs22-main-22.23.1-2.hum1
- nodejs25-main-25.9.0-1.1.hum1
- nodejs20-main-20.20.2-1.hum1
- RHSA-2026:35841
- RHSA-2026:35842
- RHSA-2026:39868
- RHSA-2026:41947
- RHSA-2026:35891
- RHSA-2026:35892
- RHSA-2026:33866
- RHSA-2026:34478
- RHSA-2026:35272
- RHSA-2026:7378
- RHSA-2026:9455
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Official advisory · high-confidence parse· fetched 13 days 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.