HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 90954 busybox busybox dpkg deb extraction root escape
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 7.8CVE-2026-90954

Busybox: busybox: dpkg-deb extraction-root escape via per-ar-member deferred symlink flushCVE-2026-90954

Answer in brief

CVE-2026-90954 records a High severity (CVSS 7.8) vulnerability in Busybox: busybox: dpkg-deb extraction-root escape via per-ar-member deferred symlink flush. The current sources do not mark it as known exploited. The current feed maps Red Hat/busybox (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 14, 2026Updated Oct 14, 2026Source checked Oct 15, 2026First seen by HOL Oct 14, 2026Material review Oct 14, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
1 mapped package or product
Fix availability
Not reported

Why this deserves its current priority

CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/busybox (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Red Hat/busyboxgeneric*Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Red Hat/busybox.
  2. 2Review the reported fix. Source-reported workaround: 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).

Evidence timeline and material changes

  1. Published upstream

    Oct 14, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Oct 14, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Oct 14, 2026

Sources and claim methodology

  • Source referenceaccess.redhat.com
  • Source referencebugzilla.redhat.com
Upstream source 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.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • WordPress Broken Link Checker plugin <= 2.4.14.1 - Content Injection vulnerabilitySame generic ecosystem
  • Path traversal via logging configuration in P4SearchSame generic ecosystem
  • Incomplete dangerous-extension list in PeaZip object open allows execution of a program or command from a crafted archive entry without confirmationSame generic ecosystem
  • Path traversal in PeaZip object preview allows execution of arbitrary programs via a crafted archive entry nameSame generic ecosystem
  • WordPress User Registration plugin <= 5.2.8 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • Cross-Site Scripting via ListBox Bound Text in Kendo UI for jQuerySame generic ecosystem

Record context

Vulnerability class
Path Traversal
EPSS
Not reported
CWE IDs
CWE-59
Source
CVE List V5
Source checked
Oct 15, 2026
References
2 linked sources
Open source record