# CVE-2026-84841: tsi-coop tsi-dpdp-cms client-side enforcement of server-side security


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 5 Sep 2026
- **Also known as:** GHSA-xvjh-cx5w-2fp2

## What is CVE-2026-84841?

CVE-2026-84841 is a medium-severity vulnerability in tsi-coop tsi-dpdp-cms, published on 2 Sep 2026. 

### Official description

A security flaw has been discovered in tsi-coop tsi-dpdp-cms up to 0.5.0. This vulnerability affects unknown code. The manipulation results in client-side enforcement of server-side security. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 0.5.1 is able to resolve this issue. It is recommended to upgrade the affected component.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

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


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

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

## Is CVE-2026-84841 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84841 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84841 is a medium-severity vulnerability in tsi-coop tsi-dpdp-cms, published on 2 Sep 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84841 exists.

Affected product: tsi-coop tsi-dpdp-cms. 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-84841/ (Markdown: https://insights.sbomify.com/CVE-2026-84841/index.md)
```

## Sources

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

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