Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Release nodejs-22.23.2-3.el10_2 ALSA-2026:75864

Open
#3,742 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
nodejs
Domain
release

Research direction

This issue announces a Node.js security update and lists affected packages and CVEs, but does not identify a repository file or request a specific change. Start by checking the repository's release-update process and whether this announcement needs action; done is not defined by the issue itself.

Written by the indexing model from the issue text.

Description

nodejs22 security update
Severity: Important
Description
Node.js is a platform built on Chrome's JavaScript runtime \ for easily building fast, scalable network applications. \ Node.js uses an event-driven, non-blocking I/O model that \ makes it lightweight and efficient, perfect for data-intensive \ real-time applications that run across distributed devices.

Security Fix(es):

  • pacote: Pacote: Denial of Service via crafted spec.rawSpec value in addGitSha function (CVE-2026-9496)
  • undici: undici: Denial of Service via unrequested WebSocket subprotocol (CVE-2026-19534)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Affected packages:
nodejs-22.23.2-3.el10_2.x86_64
nodejs-devel-22.23.2-3.el10_2.x86_64
nodejs-docs-22.23.2-3.el10_2.noarch
nodejs-full-i18n-22.23.2-3.el10_2.x86_64
nodejs-libs-22.23.2-3.el10_2.x86_64
nodejs-npm-10.9.8-1.22.23.2.3.el10_2.x86_64
nodejs-22.23.2-3.el10_2.s390x
nodejs-devel-22.23.2-3.el10_2.s390x
nodejs-docs-22.23.2-3.el10_2.noarch
nodejs-full-i18n-22.23.2-3.el10_2.s390x
nodejs-libs-22.23.2-3.el10_2.s390x
nodejs-npm-10.9.8-1.22.23.2.3.el10_2.s390x
nodejs-22.23.2-3.el10_2.ppc64le
nodejs-devel-22.23.2-3.el10_2.ppc64le
nodejs-docs-22.23.2-3.el10_2.noarch
nodejs-full-i18n-22.23.2-3.el10_2.ppc64le
nodejs-libs-22.23.2-3.el10_2.ppc64le
nodejs-npm-10.9.8-1.22.23.2.3.el10_2.ppc64le
nodejs-22.23.2-3.el10_2.aarch64
nodejs-devel-22.23.2-3.el10_2.aarch64
nodejs-docs-22.23.2-3.el10_2.noarch
nodejs-full-i18n-22.23.2-3.el10_2.aarch64
nodejs-libs-22.23.2-3.el10_2.aarch64
nodejs-npm-10.9.8-1.22.23.2.3.el10_2.aarch64
nodejs-22.23.2-3.el10_2.x86_64_v2
nodejs-devel-22.23.2-3.el10_2.x86_64_v2
nodejs-full-i18n-22.23.2-3.el10_2.x86_64_v2
nodejs-libs-22.23.2-3.el10_2.x86_64_v2
nodejs-npm-10.9.8-1.22.23.2.3.el10_2.x86_64_v2
nodejs-docs-22.23.2-3.el10_2.noarch

Dominant language
No language data
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AlmaLinux/updates

All issues in AlmaLinux/updates

Similar issues

More Release issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.