CVE-2026-14966
Last modified
CVE-2026-14966 is a low-severity vulnerability rated 3.1/10 on the CVSS scale. 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 the unix mode, as produced by legacy versions of p7zip. Such an archive, downloaded and extracted during a scan (for example via filedownload), bypassed the guard and caused an attacker-controlled symlink to be written into the extraction directory. EPSS estimates a 0.29% chance of exploitation in the next 30 days.
Description
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 the unix mode, as produced by legacy versions of p7zip. Such an archive, downloaded and extracted during a scan (for example via filedownload), bypassed the guard and caused an attacker-controlled symlink to be written into the extraction directory. The effect is limited to planting the symlink (its target is not written through), and only hosts using such a legacy p7zip build are affected; current mainline 7-Zip is not.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Blacklanternsecurity | Bbot | >= 2.3.1, <= 2.8.6 | — |
| Blacklanternsecurity | Bbot | 3.0.0.0 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.647 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.649 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.652 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.654 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.659 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.669 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.671 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.673 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.691 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.765 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.767 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.773 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.782 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.786 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.793 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.795 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.798 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.819 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.821 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.829 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.836 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.849 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.851 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.858 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.870 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.876 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.884 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.897 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.903 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.907 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.909 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.981 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.986 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1056 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1062 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1064 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1068 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1070 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1079 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1137 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1139 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1141 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1153 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1173 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1184 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1190 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1254 | Rc |
| Blacklanternsecurity | Bbot | 3.0.0.1271 | Rc |
Showing 50 of 63 affected configurations. See NVD for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-14966?
How severe is CVE-2026-14966?
How do I fix CVE-2026-14966?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-14958IBM Aspera Faspex 5 5.0.0 through 5.0.15.4 could allow a rem…7.2
- CVE-2026-14959IBM Aspera Faspex 5 5.0.0 through 5.0.15.4 could allow a rem…7.2
- CVE-2026-1496Vulnerable versions of Coverity Connect lack an error handle…9.3
- CVE-2026-14960Pegatron `Tdelo64.sys` improperly exposes privileged hardwar…9.8
- CVE-2026-14961Pegatron `Tdelo64.sys` exposes a privileged device interface…6.2
- CVE-2026-14962The ELEX WooCommerce Request a Quote WordPress plugin before…8.6
- CVE-2026-14967BBOT's `github_workflows` module could be induced to write a…3.1
- CVE-2026-14969A flaw was found in 389-ds-base where the LDBM backend attri…4.4
- CVE-2026-1497Incorrect resolving of namespaces in composite databases in …7.2
- CVE-2026-14970IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 NIM server pro…7.5
- CVE-2026-14971IBM PowerVM Novalink 2.2.02.2.12.2.1.1, and 2.3.02.3.0.12.3.…7
- CVE-2026-14973IBM Aspera Desktop App 1.0.5 through 1.0.19 IBM Aspera for d…9.3
Are you affected by CVE-2026-14966?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST