BBOT: Path traversal (Zip-Slip) in unarchive module - incomplete fix for CVE-2025-10284

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-12565: 0.21% estimated exploitation activity in the next 30 days; percentile 11.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The unarchive internal module's archive extraction commands perform no code-level validation on extracted file paths, relying entirely on the behavior of external tools (e.g. GNU tar) which varies by platform. While CVE-2025-10284 addressed git-specific RCE vectors, the underlying archive extraction path traversal was never fixed. On systems with GNU tar < 1.34 (Ubuntu 20.04, Debian Buster, CentOS 7, many Docker base images), a malicious archive can write files outside the intended extraction directory.

Published by the source

18 Jun 2026, 15:02 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:45 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3vgw-585j-4m45

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3vgw-585j-4m45

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-12565

Advisory: BBOT: Path traversal (Zip-Slip) in unarchive module - incomplete fix for CVE-2025-10284
IDs: CVE-2026-12565, GHSA-3vgw-585j-4m45
Record: https://patchnext.com/advisories/cve-2026-12565 (revision 2, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: bbot 2.8.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI bbot: affected >= 2.3.1, <= 2.8.4; fixed in 2.8.5

## Suggested inspection (read-only)
- `python -m pip show bbot`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on bbot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3vgw-585j-4m45 (OSV record GHSA-3vgw-585j-4m45 lists affected ranges: PyPI bbot >=2.3.1 <2.8.5 (fixed))
- Verified: https://github.com/advisories/GHSA-3vgw-585j-4m45 (GitHub-reviewed advisory GHSA-3vgw-585j-4m45 lists affected ranges: PyPI bbot >=2.3.1 <=2.8.4)

Commands are suggestions: review each one before running it.