# BBOT's unarchive module rejects archives containing symlink entries before extraction, but for zip and 7z archives it failed to detect symlinks whose listing carries a DOS-attribute prefix before t...

Advisory record · `GHSA-xpf3-p7gm-7756`

- **Identifiers:** `GHSA-xpf3-p7gm-7756` · `CVE-2026-14966` · `PYSEC-2026-3719`
- **State:** Confirmed
- **Severity:** CVSS 3.1 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-59](https://cwe.mitre.org/data/definitions/59.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 8 Jul 2026
- **Updated:** 15 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Jul 2026, 16:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `bbot` (PyPI): affected `>=2.3.1, <3.0.0`; fixed in `3.0.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> BBOT versions from 2.3.1 before 3.0.0 are affected. Its unarchive module failed to reject zip and 7z archives containing symlink entries when the listing carried a DOS-attribute prefix, as produced by some legacy p7zip builds. An attacker who can get such an archive downloaded and extracted during a scan, for example through filedownload, can cause an attacker-controlled symlink to be written into the extraction directory; the symlink's target is not written through. Upgrade to BBOT 3.0.0 or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.1 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N`, from CNA (BLSOPS)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0038, the 32nd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:08 UTC: First seen by agentprime
- 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-3719)

## Sources

- [GitHub Advisory Database: GHSA-xpf3-p7gm-7756](https://github.com/advisories/GHSA-xpf3-p7gm-7756)
- [OSV: GHSA-xpf3-p7gm-7756](https://osv.dev/vulnerability/GHSA-xpf3-p7gm-7756)
- <https://github.com/blacklanternsecurity/bbot/commit/a3f1a2292e2b0a553827c6175b761abe28807735>
- <https://github.com/advisories/GHSA-xpf3-p7gm-7756>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xpf3-p7gm-7756>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xpf3-p7gm-7756/>. Everything for agents: <https://agentprime.io/llms.txt>.
