---
id: "CVE-2026-101272"
kind: "vulnerability"
aliases: ["CVE-2026-101272"]
title: "Product unknown: file shredding protection ignores per-user API token binding"
severity: "low"
cvss: 2.3
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["api-tokens", "other"]
not_affected_if: []
published_at: "2026-10-28T11:17:13+00:00"
first_seen_at: "2026-10-28T11:32:27+00:00"
updated_at: "2026-10-28T11:33:46+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-101272", "first_seen_at": "2026-10-28T11:32:27+00:00"}]
---

# Product unknown: file shredding protection ignores per-user API token binding

Files created during a shredding process are not correctly bound to the authentication method, so every token-based API user gets the same session token. The files are referenced by random UUIDs and exist only for a day, so the sources rate the practical risk as virtually none.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-10-28T11:32:27+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-101272

## From the sources

The mechanism binding files generated during a shredding process to the authentication method is not working correctly and the same session token is used for all token-based API users. This is similar to an issue fixed in 2026.7.1 but was missed while creating the fix. Since the files are referred to by randomly generated UUIDs and only exist for a day, there is virtually no risk, but it renders the added protection mechanism useless. As part of the fix, we have also improved hardening of some other related code areas.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_