Bug 2498662 - CVE-2026-53655 sgx-pccs: node-tar: File smuggling due to inconsistent tar archive parsing [fedora-all]
Summary: CVE-2026-53655 sgx-pccs: node-tar: File smuggling due to inconsistent tar arc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sgx-pccs
Version: 45
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact:
URL:
Whiteboard: {"flaws": ["7abc3652-346a-4378-8182-5...
Depends On:
Blocks: CVE-2026-53655
TreeView+ depends on / blocked
 
Reported: 2026-07-09 20:05 UTC by Jon Weiser
Modified: 2026-11-18 01:56 UTC (History)
1 user (show)

Fixed In Version: sgx-pccs-1.27-2.fc45 sgx-pccs-1.27-2.fc44 sgx-pccs-1.27-2.fc43
Clone Of:
Environment:
Last Closed: 2026-11-18 01:06:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jon Weiser 2026-07-09 20:05:57 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Aoife Moloney 2026-08-17 15:16:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.

Comment 2 Daniel Berrangé 2026-11-09 17:17:42 UTC
Addressed in 1.27 rebase

$ jq '.packages."node_modules/tar".version' sgx-pccs-1.27-build/confidential-computing.tee.dcap.pccs-DCAP_1.27/service/package-lock.json 
"7.5.22"

Comment 3 Fedora Update System 2026-11-09 17:35:47 UTC
FEDORA-2026-069bc15d81 (sgx-pccs-1.27-2.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-069bc15d81

Comment 4 Fedora Update System 2026-11-09 18:11:54 UTC
FEDORA-2026-7277fc13ac (sgx-pccs-1.27-2.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-7277fc13ac

Comment 5 Fedora Update System 2026-11-09 19:52:23 UTC
FEDORA-2026-d015d281d3 (sgx-pccs-1.27-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-d015d281d3

Comment 6 Fedora Update System 2026-11-10 02:18:34 UTC
FEDORA-2026-069bc15d81 has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-069bc15d81`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-069bc15d81

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2026-11-10 02:53:28 UTC
FEDORA-2026-7277fc13ac has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-7277fc13ac`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-7277fc13ac

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2026-11-10 03:15:47 UTC
FEDORA-2026-d015d281d3 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-d015d281d3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d015d281d3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2026-11-18 01:06:22 UTC
FEDORA-2026-069bc15d81 (sgx-pccs-1.27-2.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2026-11-18 01:29:31 UTC
FEDORA-2026-7277fc13ac (sgx-pccs-1.27-2.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2026-11-18 01:56:44 UTC
FEDORA-2026-d015d281d3 (sgx-pccs-1.27-2.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.