CVE-2026-61738: SOCFortress CoPilot: Arbitrary Host File Write as Root via Path Traversal in the ScoutSuite GCP Report 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-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to 0.1.77, `POST /api/scoutsuite/generate-gcp-report` in `backend/app/integrations/scoutsuite/routes/scoutsuite.py` admits admin and analyst users and validates the uploaded content as `GCPScoutSuiteJSON`, but passes raw `file.filename` from the multipart header to `save_file_to_directory` in `backend/app/integrations/scoutsuite/services/scoutsuite.py`. The writer combines this filename with `scoutsuite-report` using `os.path.join` without sanitization or a resolved-path containment check. A traversal filename therefore writes the supplied JSON outside the intended report directory. In the reported root-running backend, the researcher demonstrated root-owned writes outside that directory and into the application source directory. This permits host-file overwrite subject to the accepted JSON-content constraint and can disrupt application operation; the demonstrated primitive does not establish unrestricted executable contents or unconditional cross-tenant confidentiality loss. Version 0.1.77 removes caller-controlled filenames from the affected route; unrestricted-content and direct-code-execution claims require separate curator reconciliation.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-30).
Weakness: CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’); CWE-73: External Control of File Name or Path; CWE-434: Unrestricted Upload of File with Dangerous Type
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 4 references on Exploit Observer
Live scores
- EPSS
- 0.006
low predicted chance of attack - VEDAS
- 0.985
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| socfortress CoPilot | version < 0.1.77 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-61738 SOCFortress CoPilot ScoutSuite - Path Traversal File Write via Upload Filename. 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-61738 SOCFortress CoPilot ScoutSuite - Path Traversal File Write via Upload Filename"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/generate-gcp-report"; nocase; fast_pattern; http.request_body; content:"filename="; nocase; pcre:"/filename=\x22[^\x22]*\.\./i"; classtype:web-application-attack; reference:cve,CVE-2026-61738; reference:url,https://www.exploit.observer/?keyword=CVE-2026-61738&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=socfortress&match=exact; sid:1104603; rev:1;)
CVE-2026-61738.rules on GitHub
References
Other references
- https://github.com/socfortress/CoPilot/security/advisories/GHSA-q3g8-3cf7-744f (x_refsource_CONFIRM)
- https://github.com/socfortress/CoPilot/pull/940 (x_refsource_MISC)
- https://github.com/socfortress/CoPilot/pull/941 (x_refsource_MISC)
- https://github.com/socfortress/CoPilot/commit/1881ef8d28bc7f45ffa88d7ba4fcca7302355508 (x_refsource_MISC)
- https://github.com/socfortress/CoPilot/commit/bfa630b65d554670c7462a32ce6fd4e3cbd0254c (x_refsource_MISC)
- https://github.com/socfortress/CoPilot/tree/v0.1.77 (x_refsource_MISC)
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.
Supporting partners
