Live › vulnerability › CVE-2026-101272
Go to dashboardFiles 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-101272")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.