Evidence record / deepseek-harness

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-deepseek-harness-cve-2026-108789-concerns-a-trusted-workflow-vm-already-replaced-by-sandboxed-ptc

CVE-2026-108789 concerns a trusted workflow VM already replaced by sandboxed PTC. A new advisory concerns an old workflow worker that trusted generated scripts inside a VM with host-realm integration. The reported consequence is access to the worker’s files/processes/network as the harness user, requiring workflow execution. The current rc already uses sandboxed PTC instead. No vendor CVE-specific fixed-version designation was found.

Channel: docs-only publication; architectural replacement already on current rc. Half: both. Date: 2026-10-12T02:15:31Z (CVE); GHSA at 03:32:56Z.

Operator consequence: Inventory and replace old workflow-worker deployments. Do not translate the database’s remote-attack label into unauthenticated network access, or treat the earlier replacement as a newly shipped October 12 fix. A vendor mapping or controlled reproducer would settle CVE-specific fix status.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-deepseek-harness-cve-2026-108789-concerns-a-trusted-workflow-vm-already-replaced-by-sandboxed-ptc

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact