CVE-2026-92748: BC Security Empire before 6.7.1 Path Traversal File Upload RCE
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
BC Security Empire before 6.7.1 fails to validate the multipart filename parameter in upload endpoints, allowing authenticated operators to write files to arbitrary paths on the C2 server. Attackers can use path traversal sequences in the filename to bypass directory containment and write malicious files to sensitive locations for code execution.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-09-16).
Weakness: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-81020, GHSA-6h6w-7p6f-xrh3
VEDAS cluster: VEDAS:DERVISHDRAGON
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-92748.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-92748.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-92748.rules
Vulnerability databases and vendor advisories (3)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-81020
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-6h6w-7p6f-xrh3
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-92748
3 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.008
low predicted chance of attack - VEDAS
- 0.986
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| BC-SECURITY Empire | before 6.7.1 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 6.7.1.
Vendor guidance:
- fix(api): block path traversal in file upload endpoints (patch)
- Empire v6.7.1 Release Notes (release-notes)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-92748 BC Security Empire - Upload Filename Path Traversal. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-92748 BC Security Empire - Upload Filename Path Traversal"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/v2/downloads"; nocase; fast_pattern; http.request_body; content:"filename="; nocase; pcre:"/filename=\x22?[^\x22&\r\n]*(\.\.(\x2f|\x5c|%2f))/i"; classtype:web-application-attack; reference:cve,CVE-2026-92748; reference:url,https://www.exploit.observer/?keyword=CVE-2026-92748&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=empire&match=exact; sid:1099609; rev:1;)
CVE-2026-92748.rules on GitHub
References
Vendor advisories and patches
- fix(api): block path traversal in file upload endpoints (patch)
- Empire v6.7.1 Release Notes (release-notes)
Exploits and technical analysis
- GitHub Issue #824 (issue-tracking)
- create_download builds the destination from the client-supplied multipart filename (technical-description)
- VulnCheck Advisory: BC Security Empire before 6.7.1 Path Traversal File Upload RCE (third-party-advisory)
Other references
- https://github.com/BC-SECURITY/Empire (product)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.