Skip to main content

CVE-2026-77369daptin insecure direct object reference

Schedule itCritical9.6EPSS not scored yet

CVE-2026-77369 is a insecure direct object reference in daptin, rated critical (9.6 on CVSS 3.1).

Why this priority: Critical severity, with no exploitation signal yet.

Published · Updated · NVD status: Deferred

What it is

Changing an identifier in a request reaches another user's records. An action never checks whether the caller is allowed to perform it.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects and change data or behaviour. In practice, this kind of flaw lets an attacker reach data or actions their role should not allow. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade daptin to 0.12.30 or later.
  2. Until it is patched, review who holds accounts that can reach it.

Description from NVD

Daptin is a GraphQL/JSON-API headless CMS. From 0.11.4 until 0.12.30, the generic GET /yjs/:documentName WebSocket route in InitializeYjsResources requires a session but does not authorize the database resource selected by a typename.referenceId.columnName room name. The YJS initial-content provider then reads the selected file.* column without CanRead or CanUpdate checks, and bidirectional synchronization allows a low-privileged authenticated user to read or modify restricted row content. Unauthenticated requests are rejected, and standalone non-canonical room names remain shared-by-name rooms. This issue is fixed in version 0.12.30.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
  • Multi-tenant services. The flaw sits between one role or tenant and another.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.

Questions to answer about your own systems

  • Where does daptin run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.