dbcve.org
CWE-602Weakness · CWE-602

CVE-2026-42160

CRITICAL · 10.0 CVSS v4.0 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Data Space Portal has an insufficient authorization vulnerability in its backend where self-registered accounts with 'PENDING' status (both organizations and users) can access or modify resources they should not be authorized to access. This allows unauthorized individuals to bypass intended access controls during the account approval workflow.

MitigationUpgrade to version 7.3.2 or later. Until upgraded, disable or restrict functionality accessible to PENDING status accounts and implement additional authorization checks at every backend endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Data Space Portal installation and version
    Locate the Data Space Portal application and determine its installed version by checking application metadata, about page, or version file. Common paths may include /opt/datspace, /app, or the application root directory.
    Affected if Installed version is lower than 7.3.2 and the application uses PENDING status accounts
  2. Check for self-registered PENDING accounts
    Query the user or organization database/tables for accounts where the status field equals 'PENDING'. This typically involves checking tables named users, organizations, accounts, or similar. Look for accounts created through self-registration workflows.
    Affected if There are accounts with PENDING status in the system
  3. Verify authorization controls for PENDING accounts
    Inspect backend endpoint authorization logic or attempt to access resources using a PENDING account (if test accounts are available). Check if endpoints validate account status before granting resource access.
    Affected if PENDING accounts can access or modify resources beyond what is intended for unapproved accounts
  4. Review account approval workflow configuration
    Examine the application configuration or database to understand how PENDING accounts are handled. Look for settings controlling what unauthenticated or pending users can access.
    Affected if The system allows PENDING accounts to bypass intended access controls during the approval workflow

A user is affected if running a Data Space Portal version below 7.3.2 and the system contains self-registered accounts with PENDING status that can access resources beyond their intended authorization level.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 7.3.2 or later. Until upgraded, disable or restrict functionality accessible to PENDING status accounts and implement additional authorization checks at every backend endpoint.

Recommended fix High confidence

7.3.2

  1. 1. Identify the currently installed Data Space Portal version using your package manager or deployment configuration.
  2. 2. Back up your current Data Space Portal installation including database and configuration files.
  3. 3. Stop the Data Space Portal service to prevent data inconsistency during upgrade.
  4. 4. Upgrade Data Space Portal to version 7.3.2 or later using your package manager or deployment mechanism (e.g., Docker, Helm, or direct binary upgrade).
  5. 5. Verify the upgrade completed successfully by checking the application version.
  6. 6. Start the Data Space Portal service and verify all services are running.
  7. 7. Test user registration and authorization flows to confirm the patch is working correctly.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42160 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42160 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data