{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90954 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-90954 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-90954 is a high-severity path traversal vulnerability in Red Hat Hardened Images, published on 14 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-90954 and fix it if it is affected.\n\nWhat it is: CVE-2026-90954 is a high-severity path traversal vulnerability in Red Hat Hardened Images, published on 14 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-90954 in the wild and no public exploit code.\n\nAffected product: Red Hat Hardened Images. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90954/ (Markdown: https://insights.sbomify.com/CVE-2026-90954/index.md)","id":"CVE-2026-90954","markdown":"https://insights.sbomify.com/CVE-2026-90954/index.md","name":"CVE-2026-90954","record":{"aliases":["AZL-109776","DEBIAN-CVE-2026-90954","GHSA-68qr-37mv-cwhv","UBUNTU-CVE-2026-90954"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BusyBox utility","requires_auth":"none","summary":"An attacker can write arbitrary files outside the extraction directory by crafting a malicious .deb archive exploiting symlink handling in BusyBox.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"A flaw was found in BusyBox's dpkg-deb archive extraction. The ar archive handler flushes deferred symlinks after each archive member, unlike the tar, cpio, and unzip handlers which flush once after the last member. A specially crafted .deb archive with two data.tar members can exploit this ordering: the first member declares a symlink pointing to an absolute path (e.g., '/'), which is deferred as unsafe but flushed after the first member. The second member declares a regular file whose path traverses the now-live symlink, resulting in a file being written outside the intended extraction directory. This could allow an attacker to write arbitrary files to arbitrary locations when a user extracts a crafted .deb package.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Busybox: busybox: dpkg-deb extraction-root escape via per-ar-member deferred symlink flush","id":"CVE-2026-90954","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"MISP CLI Shell Audit Logs Lose User Identity and CLI Marker After First Lazy Model Load","id":"CVE-2026-90955"},"packages":[],"prev":{"headline":"Missing authorization in Image Optimizer","id":"CVE-2026-90953"},"products":["Red Hat Hardened Images"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Red Hat"]},"summary":"An attacker can write arbitrary files outside the extraction directory by crafting a malicious .deb archive exploiting symlink handling in BusyBox.","url":"https://insights.sbomify.com/CVE-2026-90954/"}