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

node-tar applies PAX size override to intermediary GNU long-name/long-link headers, causing tar parser interpretation differential (file smuggling)

isaacs · node-tar

Official source article: GitHub GHSA-VMF3-W455-68VH ↗. Check the applicable product and release in the original source.

6.9MediumCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

Medium 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 355 structured product or package states 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 severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

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

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict local access and enforce least privilege on affected hosts.
  • 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. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  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: As exposure requiresRemediation target: Within 365 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 355 structured product or package states 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 2 affected package states 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-tarAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenode-tarAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenode-tarVendor fix publishedDebian records a fixed source-package version for this release.7.5.16+~4.0.1-2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenode-tarVendor fix publishedDebian records a fixed source-package version for this release.7.5.16+~4.0.1-2Debian Security Tracker ↗Source updated 5 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 5 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.157.5.16GitHub advisory ↗upstream repository advisory · 15 Jun 2026
npmtarSEMVER: introduced 0; fixed 7.5.167.5.16OSV 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-53655 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynode-tar: node-tar: File smuggling due to inconsistent tar archive parsing
353 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
  • cryostat-openshift-console-plugin-npm as a component of Cryostat 4
  • grafana-infinity-datasource-npm as a component of Cryostat 4
  • tar as a component of Cryostat 4
  • exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence
  • rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers
  • workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator
  • workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator
  • workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator
  • openshift-lightspeed/lightspeed-agentic-sandbox-rhel9 as a component of OpenShift Lightspeed
  • openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed
  • openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines
Summary
A flaw was found in node-tar. This vulnerability arises because node-tar incorrectly applies PAX extended header size records to subsequent intermediary metadata headers, leading to a desynchronization of the tar stream cursor compared to other standard tar implementations. A remote attacker could exploit this by crafting a malicious archive, causing different interpretations of archive contents between node-tar and other tools. This could allow an attacker to hide malicious files or sensitive information from security scanners that rely on different tar parsing libraries, potentially leading to information disclosure or bypassing security controls.
Remediation
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.
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-38255

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium 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 355 structured product or package states 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 is a full-featured Tar for Node.js. Prior to 7.5.16, tar (node-tar) applies a PAX extended header's size= record (and other PAX overrides) to the next header entry of any type, including intermediary metadata headers such as a GNU long-name (L) or long-link (K) entry. Per POSIX pax, a PAX extended header (x) describes the next file entry, not the intermediary extension headers that may sit between the x header and the file it annotates. Because node-tar lets the PAX size override the byte length of an intervening L/K/x header, an attacker can desynchronize node-tar's stream cursor relative to every other mainstream tar implementation (GNU tar, libarchive/bsdtar, Python tarfile, and the now-fixed tar-rs / astral-tokio-tar). The result is a tar parser interpretation differential (CWE-436): a single crafted archive yields a different set of members under node-tar than under the reference tar tools. An attacker can use this to hide a member from one parser while it is visible to another, which defeats security tooling whose scanner and extractor disagree on archive contents (e.g. a malware/secret scanner that lists entries with one library while a downstream step extracts with another) This vulnerability is fixed in 7.5.16.

What

node-tar is a full-featured Tar for Node.js. Prior to 7.5.16, tar (node-tar) applies a PAX extended header's size= record (and other PAX overrides) to the next header entry of any type, including intermediary metadata headers such as a GNU long-name (L) or long-link (K) entry. Per POSIX pax, a PAX extended header (x) describes the next file entry, not the intermediary extension headers that may sit between the x header and the file it annotates. Because node-tar lets the PAX size override the byte length of an intervening L/K/x header, an attacker can desynchronize node-tar's stream cursor relative to every other mainstream tar implementation (GNU tar, libarchive/bsdtar, Python tarfile, and the now-fixed tar-rs / astral-tokio-tar). The result is a tar parser interpretation differential (CWE-436): a single crafted archive yields a different set of members under node-tar than under the reference tar tools. An attacker can use this to hide a member from one parser while it is visible to another, which defeats security tooling whose scanner and extractor disagree on archive contents (e.g. a malware/secret scanner that lists entries with one library while a downstream step extracts with another) This vulnerability is fixed in 7.5.16.

Why

Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.

How

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

What

node-tar is a full-featured Tar for Node.js. Prior to 7.5.16, tar (node-tar) applies a PAX extended header's size= record (and other PAX overrides) to the next header entry of any type, including intermediary metadata headers such as a GNU long-name (L) or long-link (K) entry. Per POSIX pax, a PAX extended header (x) describes the next file entry, not the intermediary extension headers that may sit between the x header and the file it annotates. Because node-tar lets the PAX size override the byte length of an intervening L/K/x header, an attacker can desynchronize node-tar's stream cursor relative to every other mainstream tar implementation (GNU tar, libarchive/bsdtar, Python tarfile, and the now-fixed tar-rs / astral-tokio-tar). The result is a tar parser interpretation differential (CWE-436): a single crafted archive yields a different set of members under node-tar than under the reference tar tools. An attacker can use this to hide a member from one parser while it is visible to another, which defeats security tooling whose scanner and extractor disagree on archive contents (e.g. a malware/secret scanner that lists entries with one library while a downstream step extracts with another) This vulnerability is fixed in 7.5.16.

Why

Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.

How

An attacker operating through local access may attempt exploitation without authentication or 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
local access → Interpretation Conflict → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-436 ↗

CWE-436: Interpretation Conflict. Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-436Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2488IBM App Connect Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260624Security Bulletin 24 June 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 24 June 2026, published on 24 June 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

d?id=CVE-2026-53189 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=CVE-2026-53374 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=CVE-2026-53391 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=CVE-2026-53392 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53550 https://www.cve.org/CVERecord?id=CVE-2026-53550 Référence CVE CVE-2026-53606 https://www.cve.org/CVERecord?id=CVE-2026-53606 Référence CVE CVE-2026-53655 https://www.cve.org/CVERecord?id=CVE-2026-53655 Référence CVE CVE-2026-54371 https://www.cve.org/CVERecord?id=CVE-2026-54371 Référence CVE CVE-2026-54411 https://www.cve.org/CVERecord?id=CVE-2026-54411 Référence CVE CVE-2026-54512 https://www.cve.org/CVERecord?id=CVE-2026-54512 Référence CVE CVE-2026-54513 https://www.cve.org/CVERecord?id=CVE-2026-54513 Référence CVE CVE-2026-54514 https://www.cve.org/CVERecord?id=CVE-2026-54514 Référence CVE CVE-2026-54515 https://www.cve.org/CVERecord?id=CVE-2026-54515 Référence CVE CVE-2026-54516 https://www.cve.org/CVERecord?id=CVE-2026-54516 Référence CVE CVE-2026-54517 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-4786 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Référence CVE CVE-2026-4867 https://www.cve.org/CVERecord?id=CVE-2026-4867 Référence CVE CVE-2026-49157 https://www.cve.org/CVERecord?id=CVE-2026-49157 Référence CVE CVE-2026-49270 https://www.cve.org/CVERecord?id=CVE-2026-49270 Référence CVE CVE-2026-49844 https://www.cve.org/CVERecord?id=CVE-2026-49844 Référence CVE CVE-2026-5038 https://www.cve.org/CVERecord?id=CVE-2026-5038 Référence CVE CVE-2026-5079 https://www.cve.org/CVERecord?id=CVE-2026-5079 Référence CVE CVE-2026-53550 https://www.cve.org/CVERecord?id=CVE-2026-53550 Référence CVE CVE-2026-53655 https://www.cve.org/CVERecord?id=CVE-2026-53655 Référence CVE CVE-2026-54500 https://www.cve.org/CVERecord?id=CVE-2026-54500 Référence CVE CVE-2026-54502 https://www.cve.org/CVERecord?id=CVE-2026-54502 Référence CVE CVE-2026-54592 https://www.cve.org/CVERecord?id=CVE-2026-54592 Référence CVE CVE-2026-54896 https://www.cve.org/CVERecord?id=CVE-2026-54896 Référence CVE CVE-2026-54897 https://www.cve.org/CVERecord?id=CVE-2026-54897 Référence CVE CVE-2026-54898 https://www.cve.org/CVERecord?id=CVE-2026-54898 Référence CVE CVE-2026-54899 https://www.cve.org/CVERecord?id=CVE-2026-54899 Référence CVE CVE-2026-54900 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-021261isaacsのnode-tarにおける解釈の競合に関する脆弱性

node-tarはNode.js向けの機能豊富なTarライブラリです。7.5.16以前のバージョンでは、tar（node-tar）はPAX拡張ヘッダーのsize=レコード（およびその他のPAX上書き）を、GNUの長い名前（L）や長いリンク（K）といった中間のメタデータヘッダーを含むあらゆるタイプの次のヘッダーエントリに適用していました。POSIX paxに従うと、PAX拡張ヘッダー（x）は次のファイルエントリを記述し、中間に存在するxヘッダーとその注釈対象のファイルの間の拡張ヘッダーには適用されません。node-tarはPAXサイズによって中間のL/K/xヘッダーのバイト長を上書きしてしまうため、攻撃者はnode-tarのストリームカーソルを他の主流のtar実装（GNU tar、libarchive/bsdtar、Python tarfile、改修済みのtar-rs / astral-tokio-tar）と異なる位置にずらすことが可能になります。その結果、tarパーサーの解釈の違い（CWE-436）が生じ、単一の細工されたアーカイブがnode-tarでは異なるメンバーセットを返し、参照用tarツールでは別のメンバーセットを返す場合があります。これにより、攻撃者はあるパーサーには表示されず別のパーサーには見えるメンバーを隠し、スキャナーと抽出ツールでアーカイブ内容の解釈が異なるセキュリティツール（例：あるライブラリでエントリを一覧し、別のライブラリで下流処理として抽出するマルウェアや秘密情報スキャナー）を回避できます。この脆弱性は7.5.16で修正されました。

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
No fixed version is explicitly recorded in the structured CVE data.
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
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.
04

Evidence and provenance

Published 22 Jun 2026 · Last source change 23 Jun 2026, 16:09 UTC · CWE-436 · Interpretation Conflict

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-38255
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

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
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; grafana-infinity-datasource-npm as a component of Cryostat 4; tar as a component of Cryostat 4; exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; openshift-lightspeed/lightspeed-agentic-sandbox-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines; openshift-service-mesh/kiali-ossmc-rhel9 as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-rhel9 as a component of OpenShift Service Mesh 3; pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed; 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-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; rhacm2/volsync-operator-bundle as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhacm2/volsync-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; tar as a component of Red Hat AMQ Broker 7; ansible-automation-platform-24/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/lightspeed-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2; and 327 more
    After
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; grafana-infinity-datasource-npm as a component of Cryostat 4; tar as a component of Cryostat 4; exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; openshift-lightspeed/lightspeed-agentic-sandbox-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines; openshift-service-mesh/kiali-ossmc-rhel9 as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-rhel9 as a component of OpenShift Service Mesh 3; pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed; 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-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; rhacm2/volsync-operator-bundle as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhacm2/volsync-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; tar as a component of Red Hat AMQ Broker 7; ansible-automation-platform-24/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/lightspeed-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2; and 323 more
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; grafana-infinity-datasource-npm as a component of Cryostat 4; tar as a component of Cryostat 4; exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; openshift-lightspeed/lightspeed-agentic-sandbox-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines; openshift-service-mesh/kiali-ossmc-rhel9 as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-rhel9 as a component of OpenShift Service Mesh 3; pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed; 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-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; rhacm2/volsync-operator-bundle as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhacm2/volsync-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; tar as a component of Red Hat AMQ Broker 7; ansible-automation-platform-24/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/lightspeed-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2; and 326 more
    After
    openshift-sandboxed-containers/osc-pccs as a component of Confidential Compute Attestation; cryostat-openshift-console-plugin-npm as a component of Cryostat 4; grafana-infinity-datasource-npm as a component of Cryostat 4; tar as a component of Cryostat 4; exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence; rhmtc/openshift-migration-ui-rhel8 as a component of Migration Toolkit for Containers; workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator; workload-availability/node-healthcheck-rhel9-operator as a component of Node HealthCheck Operator; openshift-lightspeed/lightspeed-agentic-sandbox-rhel9 as a component of OpenShift Lightspeed; openshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9 as a component of OpenShift Lightspeed; openshift-pipelines/pipelines-console-plugin-pf5-rhel9 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines; openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines; openshift-service-mesh/kiali-ossmc-rhel9 as a component of OpenShift Service Mesh 3; openshift-service-mesh/kiali-rhel9 as a component of OpenShift Service Mesh 3; pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed; 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-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; rhacm2/volsync-operator-bundle as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhacm2/volsync-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; tar as a component of Red Hat AMQ Broker 7; ansible-automation-platform-24/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-24/lightspeed-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-25/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2; and 327 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Mitigation reference recorded
ENISA EUVD · EUVD-2026-38255↗Vendor CSAF · Red Hat Product Security↗CISA Vulnrichment SSVC evidence↗Public exploit reference · GitHub GHSA-VMF3-W455-68VH↗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-53655 · cve.blacktree.nl