BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-23950High confidence

node-tar has Race Condition in Path Reservations via Unicode Ligature Collisions on macOS APFS

isaacs · node-tar

Official source article: GitHub GHSA-R6Q2-HW4H-H46W ↗. Check the applicable product and release in the original source.

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 1 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.26% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs isaacs node-tar and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-tarVendor fix publishedDebian records a fixed source-package version for this release.6.2.1+~cs7.0.8-1+deb13u1Debian Security Tracker ↗Source updated 8 Oct 2026
Debian bookwormbookworm · sourcenode-tarAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian forkyforky · sourcenode-tarVendor fix publishedDebian records a fixed source-package version for this release.6.2.1+ds1+~cs6.1.13-7Debian Security Tracker ↗Source updated 8 Oct 2026
Debian sidsid · sourcenode-tarVendor fix publishedDebian records a fixed source-package version for this release.6.2.1+ds1+~cs6.1.13-7Debian Security Tracker ↗Source updated 8 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenode-tarUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmtar<= 7.5.37.5.4GitHub advisory ↗upstream repository advisory · 16 Mar 2026
npmtarSEMVER: introduced 0; fixed 7.5.47.5.4OSV record ↗aggregator derived · 10 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-23950 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynode-tar: tar: node-tar: Arbitrary file overwrite via Unicode path collision race condition
28 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation
  • openshift-logging/kibana6-rhel8 as a component of Logging Subsystem for Red Hat OpenShift
  • rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers
  • network-observability/network-observability-console-plugin-rhel9 as a component of Network Observability Operator
  • openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed
  • openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines
  • openshift-serverless-1/kn-eventing-integrations-transform-jsonata-rhel9 as a component of OpenShift Serverless
  • 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp20/system as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2
Summary
A flaw was found in node-tar, a library for Node.js. This race condition vulnerability occurs due to incomplete handling of Unicode path collisions within the `path-reservations` system on case-insensitive filesystems, such as macOS APFS. A remote attacker can exploit this by providing a specially crafted tar archive containing filenames that cause these collisions, bypassing internal concurrency safeguards. Successful exploitation can lead to arbitrary file overwrite.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-3595

No EUVD known-exploited evidence

node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the `path-reservations` system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., `ß` and `ss`), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a `PathReservations` system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently. This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using `NFD` Unicode normalization (in which `ß` and `ss` are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which `ß` causes an inode collision with `ss`)). This enables an attacker to circumvent internal parallelization locks (`PathReservations`) using conflicting filenames within a malicious tar archive. The patch in version 7.5.4 updates `path-reservations.js` to use a normalization form that matches the target filesystem's behavior (e.g., `NFKD`), followed by first `toLocaleLowerCase('en')` and then `toLocaleUpperCase('en')`. As a workaround, users who cannot upgrade promptly, and who are programmatically using `node-tar` to extract arbitrary tarball data should filter out all `SymbolicLink` entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the `path-reservations` system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., `ß` and `ss`), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a `PathReservations` system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently. This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using `NFD` Unicode normalization (in which `ß` and `ss` are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which `ß` causes an inode collision with `ss`)). This enables an attacker to circumvent internal parallelization locks (`PathReservations`) using conflicting filenames within a malicious tar archive. The patch in version 7.5.4 updates `path-reservations.js` to use a normalization form that matches the target filesystem's behavior (e.g., `NFKD`), followed by first `toLocaleLowerCase('en')` and then `toLocaleUpperCase('en')`. As a workaround, users who cannot upgrade promptly, and who are programmatically using `node-tar` to extract arbitrary tarball data should filter out all `SymbolicLink` entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

What

node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the `path-reservations` system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., `ß` and `ss`), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a `PathReservations` system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently. This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using `NFD` Unicode normalization (in which `ß` and `ss` are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which `ß` causes an inode collision with `ss`)). This enables an attacker to circumvent internal parallelization locks (`PathReservations`) using conflicting filenames within a malicious tar archive. The patch in version 7.5.4 updates `path-reservations.js` to use a normalization form that matches the target filesystem's behavior (e.g., `NFKD`), followed by first `toLocaleLowerCase('en')` and then `toLocaleUpperCase('en')`. As a workaround, users who cannot upgrade promptly, and who are programmatically using `node-tar` to extract arbitrary tarball data should filter out all `SymbolicLink` entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

Why

The product does not properly handle when an input contains Unicode encoding.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the `path-reservations` system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., `ß` and `ss`), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a `PathReservations` system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently. This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using `NFD` Unicode normalization (in which `ß` and `ss` are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which `ß` causes an inode collision with `ss`)). This enables an attacker to circumvent internal parallelization locks (`PathReservations`) using conflicting filenames within a malicious tar archive. The patch in version 7.5.4 updates `path-reservations.js` to use a normalization form that matches the target filesystem's behavior (e.g., `NFKD`), followed by first `toLocaleLowerCase('en')` and then `toLocaleUpperCase('en')`. As a workaround, users who cannot upgrade promptly, and who are programmatically using `node-tar` to extract arbitrary tarball data should filter out all `SymbolicLink` entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

Why

The product does not properly handle when an input contains Unicode encoding.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Handling of Unicode Encoding → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-176 ↗

CWE-176: Improper Handling of Unicode Encoding. The product does not properly handle when an input contains Unicode encoding.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CLowConfidentiality impact: A successful attack can cause a limited loss.IHighIntegrity impact: A successful attack can cause a major loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-176Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-3595Official EUVD mapping

node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the `path-reservations` system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., `ß` and `ss`), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a `PathReservations` system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently. This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using `NFD` Unicode normalization (in which `ß` and `ss` are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which `ß` causes an inode collision with `ss`)). This enables an attacker to circumvent internal parallelization locks (`PathReservations`) using conflicting filenames within a malicious tar archive. The patch in version 7.5.4 updates `path-reservations.js` to use a normalization form that matches the target filesystem's behavior (e.g., `NFKD`), followed by first `toLocaleLowerCase('en')` and then `toLocaleUpperCase('en')`. As a workaround, users who cannot upgrade promptly, and who are programmatically using `node-tar` to extract arbitrary tarball data should filter out all `SymbolicLink` entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3461HCL BigFix Service Management: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in HCL BigFix ausnutzen, um Sicherheitsmaßnahmen zu umgehen, erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Daten offenzulegen oder zu manipulieren, SQL-Injection- oder Cross-Site-Scripting-Angriffe durchzuführen oder serverseitige Request-Forgery- sowie Brute-Force- und Session-Hijacking-Angriffe auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1229Atlassian Bamboo, Bitbucket, Confluence, Jira: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder Cross-Site-Scripting-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0770Atlassian Jira: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren und offenzulegen, Cross-Site-Scripting-Angriffe durchzuführen oder einen Denial-of-Service-Zustand herbeizuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260121Security Bulletin 21 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 21 Jan 2026, published on 21 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

ERecord?id=CVE-2026-18401 Référence CVE CVE-2026-18446 https://www.cve.org/CVERecord?id=CVE-2026-18446 Référence CVE CVE-2026-18525 https://www.cve.org/CVERecord?id=CVE-2026-18525 Référence CVE CVE-2026-2327 https://www.cve.org/CVERecord?id=CVE-2026-2327 Référence CVE CVE-2026-2359 https://www.cve.org/CVERecord?id=CVE-2026-2359 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-23901 https://www.cve.org/CVERecord?id=CVE-2026-23901 Référence CVE CVE-2026-23903 https://www.cve.org/CVERecord?id=CVE-2026-23903 Référence CVE CVE-2026-2391 https://www.cve.org/CVERecord?id=CVE-2026-2391 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-26960 https://www.cve.org/CVERecord?id=CVE-2026-26960 Référence CVE CVE-2026-26996 https://www.cve.org/CVERecord?id=CVE-2026-26996 Référence CVE CVE-2026-27903 https://www.cve.org/CVERecord?id=CVE-2026-27903 Référence CVE CVE-2026-27904 https://www.cve.org/CVERecord?id=CVE-2026-27904 Référence CVE CVE-2026-27980 https://www.cve.org/CVERecord?id=CVE-2026-27980 Référence CVE CVE-2026-29057 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0958Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2026-22021 Référence CVE CVE-2026-22752 https://www.cve.org/CVERecord?id=CVE-2026-22752 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-2303 https://www.cve.org/CVERecord?id=CVE-2026-2303 Référence CVE CVE-2026-2332 https://www.cve.org/CVERecord?id=CVE-2026-2332 Référence CVE CVE-2026-2359 https://www.cve.org/CVERecord?id=CVE-2026-2359 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-2391 https://www.cve.org/CVERecord?id=CVE-2026-2391 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-2482 https://www.cve.org/CVERecord?id=CVE-2026-2482 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-24880 https://www.cve.org/CVERecord?id=CVE-2026-24880 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-25680 https://www.cve.org/CVERecord?id=CVE-2026-25680 Référence CVE CVE-2026-25681 https://www.cve.org/CVERecord?id=CVE-2026-25681 Référence CVE CVE-2026-25854 https://www.cve.org/CVERecord?id=CVE-2026-25854 Référence CVE CVE-2026-26960 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0901Multiples vulnérabilités dans les produits IBM

ERecord?id=CVE-2026-22029 Référence CVE CVE-2026-2332 https://www.cve.org/CVERecord?id=CVE-2026-2332 Référence CVE CVE-2026-23479 https://www.cve.org/CVERecord?id=CVE-2026-23479 Référence CVE CVE-2026-23490 https://www.cve.org/CVERecord?id=CVE-2026-23490 Référence CVE CVE-2026-2359 https://www.cve.org/CVERecord?id=CVE-2026-2359 Référence CVE CVE-2026-23631 https://www.cve.org/CVERecord?id=CVE-2026-23631 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-23865 https://www.cve.org/CVERecord?id=CVE-2026-23865 Référence CVE CVE-2026-2391 https://www.cve.org/CVERecord?id=CVE-2026-2391 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24051 https://www.cve.org/CVERecord?id=CVE-2026-24051 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-2492 https://www.cve.org/CVERecord?id=CVE-2026-2492 Référence CVE CVE-2026-25243 https://www.cve.org/CVERecord?id=CVE-2026-25243 Référence CVE CVE-2026-25589 https://www.cve.org/CVERecord?id=CVE-2026-25589 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-25645 https://www.cve.org/CVERecord?id=CVE-2026-25645 Référence CVE CVE-2026-25680 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0667Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-22036 Référence CVE CVE-2026-2229 https://www.cve.org/CVERecord?id=CVE-2026-2229 Référence CVE CVE-2026-23191 https://www.cve.org/CVERecord?id=CVE-2026-23191 Référence CVE CVE-2026-23401 https://www.cve.org/CVERecord?id=CVE-2026-23401 Référence CVE CVE-2026-23490 https://www.cve.org/CVERecord?id=CVE-2026-23490 Référence CVE CVE-2026-2359 https://www.cve.org/CVERecord?id=CVE-2026-2359 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-23865 https://www.cve.org/CVERecord?id=CVE-2026-23865 Référence CVE CVE-2026-23897 https://www.cve.org/CVERecord?id=CVE-2026-23897 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24001 https://www.cve.org/CVERecord?id=CVE-2026-24001 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-25128 https://www.cve.org/CVERecord?id=CVE-2026-25128 Référence CVE CVE-2026-25547 https://www.cve.org/CVERecord?id=CVE-2026-25547 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-2581 https://www.cve.org/CVERecord?id=CVE-2026-2581 Référence CVE CVE-2026-25896 https://www.cve.org/CVERecord?id=CVE-2026-25896 Référence CVE CVE-2026-26278 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0500Multiples vulnérabilités dans VMware Tanzu

VERecord?id=CVE-2026-1526 Référence CVE CVE-2026-1527 https://www.cve.org/CVERecord?id=CVE-2026-1527 Référence CVE CVE-2026-22036 https://www.cve.org/CVERecord?id=CVE-2026-22036 Référence CVE CVE-2026-2229 https://www.cve.org/CVERecord?id=CVE-2026-2229 Référence CVE CVE-2026-22732 https://www.cve.org/CVERecord?id=CVE-2026-22732 Référence CVE CVE-2026-22735 https://www.cve.org/CVERecord?id=CVE-2026-22735 Référence CVE CVE-2026-22737 https://www.cve.org/CVERecord?id=CVE-2026-22737 Référence CVE CVE-2026-2332 https://www.cve.org/CVERecord?id=CVE-2026-2332 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24098 https://www.cve.org/CVERecord?id=CVE-2026-24098 Référence CVE CVE-2026-24733 https://www.cve.org/CVERecord?id=CVE-2026-24733 Référence CVE CVE-2026-24734 https://www.cve.org/CVERecord?id=CVE-2026-24734 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-25219 https://www.cve.org/CVERecord?id=CVE-2026-25219 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-25854 https://www.cve.org/CVERecord?id=CVE-2026-25854 Référence CVE CVE-2026-26960 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0479Multiples vulnérabilités dans les produits Atlassian

rd?id=CVE-2023-3635 Référence CVE CVE-2023-48631 https://www.cve.org/CVERecord?id=CVE-2023-48631 Référence CVE CVE-2024-29371 https://www.cve.org/CVERecord?id=CVE-2024-29371 Référence CVE CVE-2024-45801 https://www.cve.org/CVERecord?id=CVE-2024-45801 Référence CVE CVE-2024-47875 https://www.cve.org/CVERecord?id=CVE-2024-47875 Référence CVE CVE-2025-48734 https://www.cve.org/CVERecord?id=CVE-2025-48734 Référence CVE CVE-2025-66020 https://www.cve.org/CVERecord?id=CVE-2025-66020 Référence CVE CVE-2026-22029 https://www.cve.org/CVERecord?id=CVE-2026-22029 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-25547 https://www.cve.org/CVERecord?id=CVE-2026-25547 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-26960 https://www.cve.org/CVERecord?id=CVE-2026-26960 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-31802 https://www.cve.org/CVERecord?id=CVE-2026-31802 Référence CVE CVE-2026-33870 https://www.cve.org/CVERecord?id=CVE-2026-33870 Référence CVE CVE-2026-33871 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0424Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2025-68161 Référence CVE CVE-2026-21884 https://www.cve.org/CVERecord?id=CVE-2026-21884 Référence CVE CVE-2026-21925 https://www.cve.org/CVERecord?id=CVE-2026-21925 Référence CVE CVE-2026-21932 https://www.cve.org/CVERecord?id=CVE-2026-21932 Référence CVE CVE-2026-21933 https://www.cve.org/CVERecord?id=CVE-2026-21933 Référence CVE CVE-2026-21945 https://www.cve.org/CVERecord?id=CVE-2026-21945 Référence CVE CVE-2026-22029 https://www.cve.org/CVERecord?id=CVE-2026-22029 Référence CVE CVE-2026-22030 https://www.cve.org/CVERecord?id=CVE-2026-22030 Référence CVE CVE-2026-2327 https://www.cve.org/CVERecord?id=CVE-2026-2327 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24688 https://www.cve.org/CVERecord?id=CVE-2026-24688 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-25528 https://www.cve.org/CVERecord?id=CVE-2026-25528 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-26007 https://www.cve.org/CVERecord?id=CVE-2026-26007 Référence CVE CVE-2026-26013 https://www.cve.org/CVERecord?id=CVE-2026-26013 Référence CVE CVE-2026-27024 https://www.cve.org/CVERecord?id=CVE-2026-27024 Référence CVE CVE-2026-27025 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2026-23235 Référence CVE CVE-2026-23236 https://www.cve.org/CVERecord?id=CVE-2026-23236 Référence CVE CVE-2026-23237 https://www.cve.org/CVERecord?id=CVE-2026-23237 Référence CVE CVE-2026-23238 https://www.cve.org/CVERecord?id=CVE-2026-23238 Référence CVE CVE-2026-23239 https://www.cve.org/CVERecord?id=CVE-2026-23239 Référence CVE CVE-2026-23240 https://www.cve.org/CVERecord?id=CVE-2026-23240 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-2391 https://www.cve.org/CVERecord?id=CVE-2026-2391 Référence CVE CVE-2026-23949 https://www.cve.org/CVERecord?id=CVE-2026-23949 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24001 https://www.cve.org/CVERecord?id=CVE-2026-24001 Référence CVE CVE-2026-24049 https://www.cve.org/CVERecord?id=CVE-2026-24049 Référence CVE CVE-2026-24051 https://www.cve.org/CVERecord?id=CVE-2026-24051 Référence CVE CVE-2026-24733 https://www.cve.org/CVERecord?id=CVE-2026-24733 Référence CVE CVE-2026-24734 https://www.cve.org/CVERecord?id=CVE-2026-24734 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-25500 https://www.cve.org/CVERecord?id=CVE-2026-25500 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2026-23231 Référence CVE CVE-2026-23234 https://www.cve.org/CVERecord?id=CVE-2026-23234 Référence CVE CVE-2026-23235 https://www.cve.org/CVERecord?id=CVE-2026-23235 Référence CVE CVE-2026-23236 https://www.cve.org/CVERecord?id=CVE-2026-23236 Référence CVE CVE-2026-23237 https://www.cve.org/CVERecord?id=CVE-2026-23237 Référence CVE CVE-2026-23238 https://www.cve.org/CVERecord?id=CVE-2026-23238 Référence CVE CVE-2026-23239 https://www.cve.org/CVERecord?id=CVE-2026-23239 Référence CVE CVE-2026-23240 https://www.cve.org/CVERecord?id=CVE-2026-23240 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24001 https://www.cve.org/CVERecord?id=CVE-2026-24001 Référence CVE CVE-2026-24051 https://www.cve.org/CVERecord?id=CVE-2026-24051 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-25500 https://www.cve.org/CVERecord?id=CVE-2026-25500 Référence CVE CVE-2026-25679 https://www.cve.org/CVERecord?id=CVE-2026-25679 Référence CVE CVE-2026-25702 https://www.cve.org/CVERecord?id=CVE-2026-25702 Référence CVE CVE-2026-25749 https://www.cve.org/CVERecord?id=CVE-2026-25749 Référence CVE CVE-2026-26007 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0314Multiples vulnérabilités dans les produits Atlassian

De multiples vulnérabilités ont été découvertes dans les produits Atlassian. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0281Multiples vulnérabilités dans les produits Splunk

ord?id=CVE-2026-21226 Référence CVE CVE-2026-21925 https://www.cve.org/CVERecord?id=CVE-2026-21925 Référence CVE CVE-2026-21932 https://www.cve.org/CVERecord?id=CVE-2026-21932 Référence CVE CVE-2026-21933 https://www.cve.org/CVERecord?id=CVE-2026-21933 Référence CVE CVE-2026-21945 https://www.cve.org/CVERecord?id=CVE-2026-21945 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-2391 https://www.cve.org/CVERecord?id=CVE-2026-2391 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-26981 https://www.cve.org/CVERecord?id=CVE-2026-26981 Gestion détaillée du document le 12 mars 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0249Multiples vulnérabilités dans les produits IBM

Record?id=CVE-2025-7339 Référence CVE CVE-2025-8916 https://www.cve.org/CVERecord?id=CVE-2025-8916 Référence CVE CVE-2026-1188 https://www.cve.org/CVERecord?id=CVE-2026-1188 Référence CVE CVE-2026-21441 https://www.cve.org/CVERecord?id=CVE-2026-21441 Référence CVE CVE-2026-21925 https://www.cve.org/CVERecord?id=CVE-2026-21925 Référence CVE CVE-2026-21932 https://www.cve.org/CVERecord?id=CVE-2026-21932 Référence CVE CVE-2026-21933 https://www.cve.org/CVERecord?id=CVE-2026-21933 Référence CVE CVE-2026-21945 https://www.cve.org/CVERecord?id=CVE-2026-21945 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-25765 https://www.cve.org/CVERecord?id=CVE-2026-25765 Gestion détaillée du document le 06 mars 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sy

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-004109isaacsのnode-tarにおける複数の脆弱性

node-tarはNode.js用のtarライブラリであり、バージョン7.5.3以下に競合状態の脆弱性があります。この脆弱性は、`path-reservations`システムにおけるUnicodeパスの衝突処理が不完全であることが原因です。macOSのAPFSのような大文字・小文字を区別しない、または正規化を区別しないファイルシステム上（テスト済み）では、ライブラリは衝突するパス（例: "ss"の代わりとなる特殊文字）のロックに失敗し、それらが並行して処理されることを許してしまいます。このため、ライブラリの内部並行処理防止機構が回避され、競合状態を利用したシンボリックリンク中毒攻撃が可能となります。ライブラリは同一パスのメタデータ検査とファイル操作を直列化するために`PathReservations`システムを使用していますが、この脆弱性によりエントリが同時に上書きされる競合状態が発生します。この競合状態は任意ファイルの上書きを引き起こします。この脆弱性はmacOS上（APFS/HFS+）でnode-tarを使用するユーザーおよびシステムに影響を与えます。Unicode正規化を無視するファイルシステム（例: "ss"がinode衝突を起こすAPFS）上では、衝突パスの順序が正しく維持されません。これにより攻撃者は悪意のあるtarアーカイブ内で衝突するファイル名を使用して、内部の並列ロック（`PathReservations`）を回避できます。バージョン7.5.4のパッチでは、`path-reservations.js`をターゲットファイルシステムの挙動に合わせた正規化形式（例: `NFKD`）に更新し、続いて`toLocaleLowerCase('en')`および`toLocaleUpperCase('en')`を適用しています。すぐにアップグレードできないユーザーには、プログラム的にnode-tarを使用して任意のtarballデータを展開する場合、npmが行うようにすべての`SymbolicLink`エントリをフィルタリングし、このファイルシステム上のファイル名衝突問題による任意ファイル書き込みを防御することを推奨します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
Official vendor articles2 stored documents

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 20 Jan 2026 · Last source change 1 Sept 2026, 12:04 UTC · CWE-176 · Improper Handling of Unicode Encoding

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-3595
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 7.5.4 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    node-tar: < 7.5.4 · Fixed: RHSA-2026:18480: Red Hat Enterprise Linux AppStream (v. 10)
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; openshift-logging/kibana6-rhel8 as a component of Logging Subsystem for Red Hat OpenShift; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; network-observability/network-observability-console-plugin-rhel9 as a component of Network Observability Operator; openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-serverless-1/kn-eventing-integrations-transform-jsonata-rhel9 as a component of OpenShift Serverless; 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp20/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp24/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp25/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp26/system as a component of Red Hat 3scale API Management Platform 2; rhcl-1/rhcl-console-plugin-rhel9 as a component of Red Hat Connectivity Link 1; rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub; tar.src as a component of Red Hat Enterprise Linux 6; rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; io.hawt-project as a component of Red Hat Fuse 7; rhoai/odh-dashboard-rhel8 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-dashboard-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console as a component of Red Hat OpenShift Container Platform 4; odf4/mcg-core-rhel9 as a component of Red Hat Openshift Data Foundation 4; odf4/odf-console-rhel9 as a component of Red Hat Openshift Data Foundation 4; openshift-gitops-1/argocd-rhel8 as a component of Red Hat OpenShift GitOps; satellite/iop-remediations-rhel9 as a component of Red Hat Satellite 6 · Fixed: linux-sgx-0:2.26-7.el10.src as a component of Red Hat Enterprise Linux AppStream (v. 10); linux-sgx-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); linux-sgx-debugsource-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-common-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-enclave-devel-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-libs-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-libs-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-mpa-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-mpa-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pccs-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pccs-admin-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pccs-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pckid-tool-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pckid-tool-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); tdx-attest-libs-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); tdx-qgs-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); tdx-qgs-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); linux-sgx-0:2.26-7.el9.src as a component of Red Hat Enterprise Linux AppStream (v. 9); linux-sgx-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); linux-sgx-debugsource-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-common-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-enclave-devel-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-libs-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-libs-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-mpa-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-mpa-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-pccs-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-pccs-admin-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-pccs-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-pckid-tool-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); and 10 more
    After
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; openshift-logging/kibana6-rhel8 as a component of Logging Subsystem for Red Hat OpenShift; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; network-observability/network-observability-console-plugin-rhel9 as a component of Network Observability Operator; openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-serverless-1/kn-eventing-integrations-transform-jsonata-rhel9 as a component of OpenShift Serverless; 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp20/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp24/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp25/system as a component of Red Hat 3scale API Management Platform 2; 3scale-amp26/system as a component of Red Hat 3scale API Management Platform 2; rhcl-1/rhcl-console-plugin-rhel9 as a component of Red Hat Connectivity Link 1; rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub; tar.src as a component of Red Hat Enterprise Linux 6; rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; io.hawt-project as a component of Red Hat Fuse 7; rhoai/odh-dashboard-rhel8 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-dashboard-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console-rhel9 as a component of Red Hat OpenShift Container Platform 4; odf4/mcg-core-rhel9 as a component of Red Hat Openshift Data Foundation 4; odf4/odf-console-rhel9 as a component of Red Hat Openshift Data Foundation 4; openshift-gitops-1/argocd-rhel8 as a component of Red Hat OpenShift GitOps; satellite/iop-remediations-rhel9 as a component of Red Hat Satellite 6 · Fixed: linux-sgx-0:2.26-7.el10.src as a component of Red Hat Enterprise Linux AppStream (v. 10); linux-sgx-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); linux-sgx-debugsource-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-common-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-enclave-devel-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-libs-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-libs-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-mpa-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-mpa-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pccs-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pccs-admin-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pccs-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pckid-tool-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); sgx-pckid-tool-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); tdx-attest-libs-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); tdx-qgs-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); tdx-qgs-debuginfo-0:2.26-7.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); linux-sgx-0:2.26-7.el9.src as a component of Red Hat Enterprise Linux AppStream (v. 9); linux-sgx-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); linux-sgx-debugsource-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-common-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-enclave-devel-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-libs-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-libs-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-mpa-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-mpa-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-pccs-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-pccs-admin-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-pccs-debuginfo-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); sgx-pckid-tool-0:2.26-7.el9.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9); and 10 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-3595↗Vendor CSAF · Red Hat Product Security↗Public exploit reference · GitHub GHSA-R6Q2-HW4H-H46W↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-23950 · cve.blacktree.nl