# ALSA-2026:92376: Security update for 10 packages

ALSA-2026:92376, released November 7, 2026, fixes 13 CVEs across 10 products. One of them is being exploited (CVE-2026-111497); 1 on CISA KEV. Patch Radar priority: Patch now.

- Web page: https://patchblox.com/security/fix/linux/alsa-2026-92376
- Platform: Linux
- Released: Nov 7, 2026
- Priority: Patch now (Closes CVE-2026-111497, exploited (CISA KEV))
- CVEs: 13, exploited: 1, on CISA KEV: 1
- Vendor advisory: https://osv.dev/vulnerability/ALSA-2026:92376

## Applies to

| Product | Release | Fixed in |
|---|---|---|
| [nodejs](https://patchblox.com/security/data/product/linux/nodejs.md) | almalinux 8 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| [nodejs-devel](https://patchblox.com/security/data/product/linux/nodejs-devel.md) | almalinux 8 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| [nodejs-docs](https://patchblox.com/security/data/product/linux/nodejs-docs.md) | almalinux 8 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| [nodejs-full-i18n](https://patchblox.com/security/data/product/linux/nodejs-full-i18n.md) | almalinux 8 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| [nodejs-libs](https://patchblox.com/security/data/product/linux/nodejs-libs.md) | almalinux 8 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| [nodejs-nodemon](https://patchblox.com/security/data/product/linux/nodejs-nodemon.md) | almalinux 8 | 3.1.14-2.module_el8.10.0+4250+09238ed4 |
| [nodejs-packaging](https://patchblox.com/security/data/product/linux/nodejs-packaging.md) | almalinux 8 | 2021.06-6.module_el8.10.0+4086+70facd4a |
| [nodejs-packaging-bundler](https://patchblox.com/security/data/product/linux/nodejs-packaging-bundler.md) | almalinux 8 | 2021.06-6.module_el8.10.0+4086+70facd4a |
| [npm](https://patchblox.com/security/data/product/linux/npm.md) | almalinux 8 | 1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 |
| [v8-13.6-devel](https://patchblox.com/security/data/product/linux/v8-13.6-devel.md) | almalinux 8 | 3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2026-111497](https://patchblox.com/security/data/cve/CVE-2026-111497.md) | Patch now | Google: CVE-2026-111497 Buffer overflow vulnerability in the Brotli decoder | 9.8 | 0.8264 | CISA KEV, Disclosed |
| [CVE-2026-106072](https://patchblox.com/security/data/cve/CVE-2026-106072.md) | High | A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`.  `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc.  This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. | 8.1 | 0.0062 |  |
| [CVE-2026-102278](https://patchblox.com/security/data/cve/CVE-2026-102278.md) | High | brace-expansion: DoS via uncontrolled recursion on nested brace groups causing stack exhaustion | 8.1 | 0.0049 |  |
| [CVE-2026-105482](https://patchblox.com/security/data/cve/CVE-2026-105482.md) | High | A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). This is an incomplete fix of CVE-2026-48930, which only covered dns.lookup() and the net/tls host options.  Because the name is passed to c-ares as a C string, resolving attacker.example\0.trusted.example queries attacker.example and returns its records without any error. Applications that validate a hostname, for example against a domain allowlist, and then resolve it with dns.resolve*() can act on records for a different name than the one they validated.  This vulnerability affects Node.js 26.x, 24.x, and 22.x. | 8.1 | 0.0047 |  |
| [CVE-2026-102276](https://patchblox.com/security/data/cve/CVE-2026-102276.md) | High | brace-expansion: DoS via uncontrolled recursion in parseCommaParts causing stack exhaustion | 8.1 | 0.0046 |  |
| [CVE-2026-102277](https://patchblox.com/security/data/cve/CVE-2026-102277.md) | High | brace-expansion: Quadratic-time expansion of the `{a},b}` rewrite causes CPU denial of service | 8.1 | 0.0043 |  |
| [CVE-2026-101911](https://patchblox.com/security/data/cve/CVE-2026-101911.md) | High | node-ip-address: ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript | 8.1 | 0.0038 |  |
| [CVE-2026-106074](https://patchblox.com/security/data/cve/CVE-2026-106074.md) | High | A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt()` to be saved into user-land startup snapshots (`--build-snapshot`) and single executable applications built with `useSnapshot`.  If any of these functions, or an API that relies on them such as `URL.createObjectURL()`, is called while the snapshot is built, every process started from that snapshot returns the same values until the cache is refilled: up to 127 UUIDs and about 1,000 `randomInt()` values. Identifiers expected to be unique can collide across processes, and values issued by one process can be predicted by observing another.  This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. | 8.1 | 0.0033 |  |
| [CVE-2026-105481](https://patchblox.com/security/data/cve/CVE-2026-105481.md) | High | A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. This is an incomplete fix of CVE-2026-48931.  The guard that destroys idle keep-alive sockets when unexpected data arrives only runs when the event loop polls for I/O. If an unsolicited response has already reached the socket but has not been read yet when the socket is handed to a new request, for example because the event loop was busy with synchronous work, the guard is removed without seeing it and the data is parsed as the response to the new request.  This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. | 8.1 | 0.0032 |  |
| [CVE-2026-105483](https://patchblox.com/security/data/cve/CVE-2026-105483.md) | High | A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`).  `tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.  This vulnerability affects Node.js **26.x** and **24.x**. | 8.1 | 0.0030 |  |
| [CVE-2026-106069](https://patchblox.com/security/data/cve/CVE-2026-106069.md) | High | A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`.  `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address.  This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. | 8.1 | 0.0030 |  |
| [CVE-2026-106073](https://patchblox.com/security/data/cve/CVE-2026-106073.md) | High | A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks. This is an incomplete fix of CVE-2026-21715, which only covered `fs.realpathSync.native()`.  As a result, code running under `--permission` with restricted `--allow-fs-read` can still use `fs.realpathSync()` to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories.  This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. | 8.1 | 0.0025 |  |
| [CVE-2026-106071](https://patchblox.com/security/data/cve/CVE-2026-106071.md) | High | A flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard `--allow-fs-read` or `--allow-fs-write` rule.  When the requested path is shorter than the prefix of a wildcard grant, the radix tree lookup stops comparing early and treats the path as a match. For example, `--allow-fs-read=/etc/passwd.*` also allows reading `/etc/passwd`. This requires the wildcard grant to sit directly under the root of the permission tree, for example when it is the only grant for that scope. This is a different root cause from CVE-2026-58043.  This vulnerability affects Node.js **26.x**. | 8.1 | 0.0020 |  |

---

Data as of 2026-11-07T18:46:35Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.