CVE-2026-61730 Details
Description
SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. In affected deployments, the unauthenticated `/scoutsuite-report` `StaticFiles` mount in `backend/copilot.py` exposes the `scoutsuite-report` directory even though normal /api routes require JWT authentication. Generated HTML reports and `scoutsuite-results/scoutsuite_results_<name>.js` files disclose AWS, Azure and GCP IAM principals, resource inventories, misconfigurations and findings. Report names derive from caller-selected names with predictable defaults. During an admin- or analyst-initiated GCP scan, `backend/app/integrations/scoutsuite/routes/scoutsuite.py` saves the uploaded Google service-account JSON key into that same web-served directory. In `backend/app/integrations/scoutsuite/services/scoutsuite.py`, `generate_gcp_report_background` removes the key only after the scan finishes. Any anonymous client that can reach the host and request the file path can therefore retrieve the private key during the scan and use the service account's cloud permissions, as well as read retained cloud-security reports. Credential isolation is released in version 0.1.77; a release fully remediating the report-disclosure component has not been established.
A vulnerability in SOCFortress CoPilot allows unauthenticated access to sensitive files through a static file mount. The issue arises in versions through 0.1.77, where the '/scoutsuite-report' directory is exposed without authentication, contrary to the secured '/api' routes. This directory can contain confidential information such as AWS, Azure, and GCP IAM details, resource inventories, misconfigurations, and findings. During a GCP scan, uploaded service-account JSON keys are also saved in this directory, making private keys accessible to anyone who can reach the host.
Users can upgrade to SOCFortress CoPilot version 0.2.0, which addresses the issue of credential exposure by keeping uploaded GCP keys out of the web-served directory. However, the broader issue of unauthenticated report file exposure via the static file mount has not yet been fully remediated.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 30, 2026CISA-ADP
Assessed Oct 30, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/socfortress/CoPilot/commit/bfa630b65d554670c7462a32ce6fd4e3cbd0254c | [email protected] | Source CodeVendor |
| https://github.com/socfortress/CoPilot/pull/940 | [email protected] | Issue TrackingVendor |
| https://github.com/socfortress/CoPilot/security/advisories/GHSA-pm2w-mmc3-h8hc | [email protected] | AdvisoryRemedyVendor |
| https://github.com/socfortress/CoPilot/tree/v0.1.77 | [email protected] | Source CodeVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor | [email protected] |
| CWE-306 | Missing Authentication for Critical Function | [email protected] |
| CWE-522 | Insufficiently Protected Credentials | [email protected] |
| CWE-552 | Files or Directories Accessible to External Parties | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| SOCFortress CoPilot | <= latest |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 30, 2026 | CVE Modified | CISA-ADP |
| Oct 30, 2026 | New CVE Received | [email protected] |
Volerion