CaseMark keeps its document vault out of the browser's reach

Two fixes close a gap where the keys to CaseMark's case-document store were briefly visible on the user's side.

securityinfrastructure

When you open a document to review it, the fork now passes the file through its own server before sending it to you. Previously the browser got a short-lived signed link straight to Case Vault - CaseMark's case-document store - meaning the link, and the access it granted, flashed up in the browser where a curious user (or a compromised one) could grab it. Now that handoff stays server-side and the browser only ever sees the file itself.

The same release tidies up a settings screen that could momentarily flash a false "your API key is missing" warning before it had finished loading - a small thing, but the kind that generates support tickets. CaseMark flags one tradeoff worth a look on GitHub: documents now route through its server on every view, so anyone serving large files to a busy team should watch the memory cost.

So what If you store privileged case files behind a vendor, this is the kind of plumbing that decides whether access links can leak - worth a look for anyone running document review at scale.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

3 commits from CaseMark/mikeoss-casedotdev, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
96ee1a64 Avoid false missing key state during profile load kveton 2026-05-04 ↗ GitHub
8b7e3e0a Proxy Case document display bytes kveton 2026-05-04 ↗ GitHub
303e2633 Merge pull request #6 from CaseMark/codex/fix-case-document-display Scott Kveton 2026-05-04 ↗ GitHub
Fix Case Vault document preview loading

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-36.md from inside the repo you want the changes in.

⬇ Download capture-thread-36.md