# CVE-2026-84839: tsi-coop tsi-dpdp-cms Admin Console/DPO Compliance Console web.xml missing authentication

> Attackers can bypass authentication on the Admin and DPO Compliance Consoles due to missing security configurations in web.xml, allowing unauthorized access.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-3qwp-5cgc-v46r

## What is CVE-2026-84839?

CVE-2026-84839 is a medium-severity missing authorization vulnerability in tsi-coop tsi-dpdp-cms, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in tsi-coop tsi-dpdp-cms up to 0.5.0. Affected by this issue is some unknown functionality of the file web.xml of the component Admin Console/DPO Compliance Console. Executing a manipulation can lead to missing authentication. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 0.5.1 can resolve this issue. It is suggested to upgrade the affected component.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-84839 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84839 is a medium-severity missing authorization vulnerability in tsi-coop tsi-dpdp-cms, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84839 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-84839/ (Markdown: https://insights.sbomify.com/CVE-2026-84839/index.md)
```

## Sources

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

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