Bug 2449680

Summary: CVE-2026-33056 libkrun: tar-rs: Arbitrary directory permission modification via crafted tar archive [fedora-all]
Product: [Fedora] Fedora Reporter: Jon Moroney <jmoroney>
Component: libkrunAssignee: Sergio Lopez <slopezpa>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: code, crobinso, m.kurz, slopezpa, tfanelli
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["e52268c3-21cf-4253-ace1-12d88ee6b1bf"]}
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2449490    

Description Jon Moroney 2026-03-20 17:55:45 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.

Comment 1 Ben Beasley 2026-03-22 07:45:43 UTC
More information is available at https://www.cve.org/CVERecord?id=CVE-2026-33056. This flaw is fixed in version 0.4.45 of the tar crate. Updates for rust-tar-0.4.45 are in testing for all Fedora and EPEL branches, and buildroot overrides are active. Therefore, you can fix this in Fedora at any time by simply rebuilding libkrun. I’m not going to do that now because rust-sig is not a co-maintainer, but I can do it as provenpackager if you ask me to. In RHEL, where the package uses vendored Rust crate dependencies, you would need to fix this separately within the package’s dependency bundle.

Comment 2 Sergio Lopez 2026-03-24 14:22:50 UTC
The rust-tar crate is pulled by libkrun's aws-nitro, but this feature is currently not built-in in Fedora. Cargo doesn't seem to be aware of the dependencies that are gated out behind built-time features, which is probably why it still appears in the dependency graph.