# CVE-2026-7185: Unauthorized access to files in T-Systems products


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-xm42-w58j-mp94

## What is CVE-2026-7185?

CVE-2026-7185 is a medium-severity vulnerability in T-Systems Archivo, published on 6 Jul 2026. 

### Official description

A validation vulnerability has been identified in certain web features related to file management or upload in several products of the TAO 2.0 suite. This vulnerability could allow an attacker capable of interacting with the affected feature to attempt to access file system resources outside the scope intended by the application.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-7185 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7185 is a medium-severity vulnerability in T-Systems Archivo, published on 6 Jul 2026. 
Exploitation: There is no known exploitation of CVE-2026-7185 in the wild and no public exploit code.

Affected product: T-Systems Archivo. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-7185/ (Markdown: https://insights.sbomify.com/CVE-2026-7185/index.md)
```

## Sources

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

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