# CVE-2026-61707: SOCFortress CoPilot: Stored case-report template injection permits backend code execution


- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-61707?

CVE-2026-61707 is a critical vulnerability in socfortress CoPilot, published on 29 Oct 2026. 

### Official description

SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to 0.1.76, in the reported deployment, case-report templates uploaded by `customer_user`, the lowest-privilege portal role, are later executed by non-sandboxed Jinja2 engines when an admin or analyst generates a report. The `/case-report-template/upload` route in `backend/app/incidents/routes/db_operations.py` validates only the filename-derived MIME type, not the template content. Templates share a global store without customer_code scoping, and `customer_user` can also list, download and delete them, allowing an attacker to replace a legitimate default template under the same name. In `backend/app/incidents/services/reports.py`, `render_document_with_context` uses `DocxTemplate` without a sandbox; in `backend/app/incidents/services/reports_pdf.py`, `render_html_template` uses a non-sandboxed `Environment` without autoescaping. Normal privileged requests to `POST /api/incidents/report/generate-report-docx` or `/generate-report-pdf` therefore evaluate attacker-controlled Jinja expressions as Python on the backend. The reported deployment executes commands as root, exposing all tenants' incident and SIEM data and stored connector credentials. The HTML/PDF wkhtmltopdf renderer additionally permits local-file reads and requests to internal services. This issue is fixed in version 0.1.76.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-862 (Missing Authorization), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-61707?


## How do I fix CVE-2026-61707?

No fix has been published for CVE-2026-61707 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61707 being exploited?

There is no known exploitation of CVE-2026-61707 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61707 and fix it if it is affected.

What it is: CVE-2026-61707 is a critical vulnerability in socfortress CoPilot, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-61707 in the wild and no public exploit code.

Affected product: socfortress CoPilot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61707/ (Markdown: https://insights.sbomify.com/CVE-2026-61707/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61707
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61707
- OSV: https://osv.dev/vulnerability/CVE-2026-61707

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61707/
Summaries are generated and may contain mistakes; the official description above is the record.