# CVE-2026-42160: Missing authorization in dataspace-portal

> Attackers can bypass authorization checks on pending accounts to access restricted data or escalate privileges in the Data Space Portal backend.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-989g-wpfv-6vxx

## What is CVE-2026-42160?

CVE-2026-42160 is a critical missing authorization vulnerability in sovity dataspace-portal, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Data Space Portal is an open-source Software as a Service (SaaS) solution designed to streamline Dataspace management. From version 2.1.1 to before version 7.3.2, there is insufficient authorization in the dataspace-portal backend regarding self-registered "PENDING" organization / user accounts. This issue has been patched in version 7.3.2.

Weakness: CWE-863 (Incorrect Authorization), CWE-602 (Client-Side Enforcement of Server-Side Security)

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


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

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

## Is CVE-2026-42160 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42160 is a critical missing authorization vulnerability in sovity dataspace-portal, published on 8 May 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-42160 exists.

Affected product: sovity dataspace-portal. 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-42160/ (Markdown: https://insights.sbomify.com/CVE-2026-42160/index.md)
```

## Sources

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

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