SOCFortress CoPilot: Arbitrary Host File Write as Root via Path Traversal in the ScoutSuite GCP Report Upload (RCE)
Affects SOCFortress CoPilot before 0.1.77 where the ScoutSuite GCP report upload endpoint is used with a valid GCP ScoutSuite JSON body. Fixed in 0.1.77.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 0.1.77
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SOCFortress CoPilot, a security operations platform, is affected by a path traversal flaw in its ScoutSuite GCP report upload feature. An authenticated admin or analyst can use a crafted filename to write JSON content to arbitrary locations on the host, including the application's source directory, which could overwrite files and disrupt the application's operation.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- socfortress CoPilot
fixed in 0.1.77
References 6
GitHub · socfortress/CoPilot
Questions about CVE-2026-61738
What does this mean?
The ScoutSuite GCP report upload can be abused to write files to arbitrary locations on the host as root. This can lead to code execution or disruption of the application.Source: github.com
Am I affected, and how do I check?
CoPilot versions before 0.1.77 are affected when the generate-gcp-report endpoint is used and the uploaded body passes GCP ScoutSuite JSON content validation. Check the installed CoPilot version and whether the ScoutSuite GCP report upload feature is in use.Source: github.com
What should I do about it?
Upgrade SOCFortress CoPilot to 0.1.77 or later.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data