CVE-2026-77165: Database file locking denial of service via TYPE_TOKEN locks

CVE-2026-77165 · Severity: medium · CVSS 6.5 · Published 2026-09-21

A database system fails to allow file owners to unlock resource locks created by other users, causing files to become permanently inaccessible. An attacker with any database access can lock files belonging to legitimate users, disrupting business operations with no recovery method except direct database intervention.

Technologies: <UNKNOWN>.

Quick answers

Is CVE-2026-77165 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-77165 being exploited in the wild.
How severe is CVE-2026-77165?
Medium severity, with a CVSS score of 6.5, published 21 September 2026.
Which products and versions are affected?
<UNKNOWN>.
Is there a fix for CVE-2026-77165?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-77165 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-77165?
Check whether you run <UNKNOWN>. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the file locking mechanism where TYPE_TOKEN locks placed by one user cannot be revoked or removed by the file owner or administrators. The affected component lacks proper authorization checks to allow lock removal by file owners. This results in a denial-of-service condition where locked files remain inaccessible until database-level manual intervention occurs.

Affected products

  • <UNKNOWN>

Timeline

  • 2026-09-21: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.