Description
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.
Related CPE's
Could not find any relations
Weaknesses
Could not find any weaknesses
CVSS impact metrics
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
2.3 · Low
Information
Source identifier
655498c3-6ec5-4f0b-aea6-853b334d05a6
Vulnerability status
Deferred
Published
2026-10-28T11:17:13.273Z
5 hours agoLast modified
2026-10-28T15:24:56.033Z
53 minutes ago