# CVE-2026-101272: Incorrect session validation for API-created shredder exports


- **Severity:** Low 2.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-38jm-3ffc-942j

## What is CVE-2026-101272?

CVE-2026-101272 is a low-severity vulnerability, published on 28 Oct 2026. 

### Official 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.

## Which versions are affected by CVE-2026-101272?


## How do I fix CVE-2026-101272?

No fix has been published for CVE-2026-101272 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101272 being exploited?

There is no known exploitation of CVE-2026-101272 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101272 and fix it if it is affected.

What it is: CVE-2026-101272 is a low-severity vulnerability, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-101272 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101272/ (Markdown: https://insights.sbomify.com/CVE-2026-101272/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101272
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101272
- OSV: https://osv.dev/vulnerability/CVE-2026-101272

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101272/
Summaries are generated and may contain mistakes; the official description above is the record.