{
  "id": "CVE-2026-90954",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-90954",
  "published_at": "2026-10-14T10:00:08.215Z",
  "title": "Busybox: busybox: dpkg-deb extraction-root escape via per-ar-member deferred symlink flush",
  "vendor": "Red Hat",
  "product": "Red Hat Hardened Images",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-59",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [],
  "remediation": {
    "workarounds": [
      "Do not use BusyBox dpkg-deb to extract untrusted .deb packages. Use Debian's reference dpkg-deb implementation, which treats the extraction root as a boundary and is not affected by this issue. If BusyBox dpkg-deb must be used, inspect .deb archives for multiple data.tar members before extraction (legitimate .deb packages contain exactly one data.tar member)."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
