Is there a public exploit for CVE-2026-61708?

No public exploit for CVE-2026-61708 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-61708?

CVE-2026-61708 scores CVSS 8.5 (v3.1), rated high.

8.5 High

SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs.

CVE-2026-61708

SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to 0.1.76, POST /api/agentdatastore/upload in backend/app/datastore/datastoreroutes.py permits customeruser callers to choose bucketname and objectname without an allowlist, tenant prefix, ownership check or content restriction. The only file check requires a nonempty filename. The operations in backend/app/datastore/datastoreoperations.py create missing buckets and upsert objects, allowing existing objects belonging to any tenant to be overwritten. Targets include sysmon-configs/ /sysmonconfig.xml distributed to managed Windows endpoints, copilot-case-report-templates/ rendered server-side, and case evidence or forensic artifacts under copilot-cases/ / and velociraptor-artifacts/ / / . A lowest-privilege user can tamper with cross-tenant evidence, blind endpoint telemetry, poison report templates for later code execution, plant data or exhaust storage. Sibling list, download and delete routes remain restricted to admin/analyst; the exposed operation is the upload write path. This issue is fixed in version 0.1.76.

Assessment

CVSS: 8.5 (v3.1)
Severity: High
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 30 October 2026
Last updated: 30 October 2026
Weakness: CWE-284, CWE-639, CWE-862
Assigner: security-advisories@github.com

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 4 + 2? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-61708