PULSE
FEED
ransomqilin reclama a Strategic Properties · USransomqilin reclama a The Ashland Water Group · US · Energy & Utilitiesransomqilin reclama a The National Commission on Indigenous Peoples · PH · Government & Defenseransomchaos reclama a radienzliving.com · DE · Retail & E-Commerceransomchaos reclama a amarok.com · Technologyransomvortex reclama a APELLIS · US · Healthcareransomglobal secret group reclama a Johnson Bros. Bakery Supply, Inc. · US · Agriculture and Food Productionransomcurious worm reclama a t**l**kw*****p.com · Technologyransomqilin reclama a Airways Aviation · AE · Transportationransomqilin reclama a Ayala Property Management · PH · Otherransomqilin reclama a California Cross Dock · US · Transportationransomqilin reclama a Fahrenheit DDB · PE · Professional Servicesransomqilin reclama a Hybrytec · AU · Technologyransomqilin reclama a IMS Messsysteme · DE · Manufacturingransomqilin reclama a Strategic Properties · USransomqilin reclama a The Ashland Water Group · US · Energy & Utilitiesransomqilin reclama a The National Commission on Indigenous Peoples · PH · Government & Defenseransomchaos reclama a radienzliving.com · DE · Retail & E-Commerceransomchaos reclama a amarok.com · Technologyransomvortex reclama a APELLIS · US · Healthcareransomglobal secret group reclama a Johnson Bros. Bakery Supply, Inc. · US · Agriculture and Food Productionransomcurious worm reclama a t**l**kw*****p.com · Technologyransomqilin reclama a Airways Aviation · AE · Transportationransomqilin reclama a Ayala Property Management · PH · Otherransomqilin reclama a California Cross Dock · US · Transportationransomqilin reclama a Fahrenheit DDB · PE · Professional Servicesransomqilin reclama a Hybrytec · AU · Technologyransomqilin reclama a IMS Messsysteme · DE · Manufacturing
← All CVEs
CVE WatchNov 16, 2026

CVE-2026-123353

Docmost is open-source collaborative wiki and documentation software. Prior to 0.96.0, two concurrent role-demotion requests from a space ad

CVSS

3.3

Low

EPSS

—

KEV

—

Exploit Today

—

0-100

Published: Nov 16, 2026 · Last modified: Nov 16, 2026 · CWE-362 · CWE-367

EPSS · 30d

Not enough EPSS history yet.

Technical description

Docmost is open-source collaborative wiki and documentation software. Prior to 0.96.0, two concurrent role-demotion requests from a space admin or workspace owner can each pass the last-admin or last-owner count check before either update is committed because the validation and role update are not serialized in one transaction. The requests can therefore demote the final two space admins or workspace owners and leave the affected space without an admin or the workspace without an owner, preventing normal administrative recovery. This issue is fixed in version 0.96.0.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-62336—
—
———qbee-agent is the device agent component of the qbee.io IoT device management platform. Prior to 2026.27, the privileged createFile helper followed attacker-controlled symbolic links during file creation. A local unprivileged user whose account is managed by the SSH Keys bundle could replace ~/.ssh with a link to /root/.ssh, causing the agent to write an authorized key for root. On systems using RAUC download mode with ineffective kernel symlink protection, the predictable /tmp/.bundle.raucb.part path could be linked to a system file and then overwritten or truncated during an update. A file-distribution destination beneath an attacker-controlled directory could similarly redirect the partial-download path so the agent changed ownership of a sensitive file. These vectors could result in root privilege escalation, arbitrary file modification, or denial of service. This issue is fixed in version 2026.27.5h
CVE-2026-119790—
—
———Next.js is a React framework for building full-stack web applications. From 16.3.0 until 16.4.5, Next.js applications using the same 'use cache' function directly during rendering and through unstable_cache() can disclose cached data across root params when that function reads a root param. During the first fill after a cold process start, cross-request deduplication allows a concurrent unstable_cache() request to join the direct call's in-flight fill and receive its result before the root param mismatch is rejected. unstable_cache() then persists that result under a key that omits root params, causing later requests for other root param values to receive the same entry until revalidation or eviction. Exploitation requires the unstable_cache() request to arrive while the first fill is in flight. Outside this race, nesting 'use cache' inside unstable_cache() raises an unsupported-operation error, and avoiding that nesting prevents the issue. This issue is fixed in version 16.4.5.5h
CVE-2026-119351—
—
———Next.js is a React framework for building full-stack web applications. From 16.2.0 until 16.4.5, Next.js applications with Cache Components enabled can reuse an outer 'use cache' entry across root param values when a nested 'use cache' call reads a root param through next/root-params and returns a value containing pending promises. React Flight can deliver the ready portion to the outer function before the inner cache finishes publishing its root-param dependencies. The outer entry can then complete and be persisted under a key that omits the root param, causing the first written value to be served for other root param values and allowing the outer entry to ignore nested cache tag invalidation and lifetimes. The leaked value is not attacker controlled and depends on which invocation writes the entry first. This variant does not require an existing inner cache entry or a slow cache handler and is not covered by the fix for CVE-2026-103004. This issue is fixed in version 16.4.5.5h
CVE-2026-129919—
—
———Kunai, a security monitoring tool, contains a time-of-check to time-of-use (TOCTOU) race condition in its mount namespace (mnt ns) caching logic. When resolving a security event that references a specific process PID and an expected mount namespace, the Switcher::new function read /proc/<pid>/ns/mnt to determine the target namespace and cached the result under the expected namespace key without verifying that the resolved namespace actually matched the expected one. An attacker with local access could exploit this by either (1) arranging for the referenced PID to be reused by a process in a different namespace (e.g., the host namespace) before Kunai resolves it, or (2) calling unshare or setns on the target process after the event is generated but before the namespace is resolved. In either case, the wrong namespace (potentially the host's own namespace) would be cached under the container's namespace key. The security impact is that subsequent container security events would be resolved against host filesystem paths rather than container paths. This undermines the integrity of the security monitoring data: container activity could be misattributed to the host, host activity could be misattributed to a container, and file-path-based detections or alerts would reference incorrect paths. An attacker could potentially use this to obscure malicious activity within a container by making it appear as benign host activity, or to generate misleading security alerts. The vulnerability requires local access to the system and a specific timing window between event generation and namespace resolution. No remote attack vector or user interaction is required.10h
CVE-2026-115690—
—
——0Apache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of a signed message, and the ID of a SAML 2.0 "OneTimeUse" assertion, so that a captured message cannot be accepted twice. It checked whether a value had already been seen, validated the message, and only then remembered the value, as two separate steps. If several copies of the same message were processed at the same time, they could all pass the check before any of them was remembered, and all be accepted. An attacker who obtained a valid message before the recipient first processed it could send several copies at once, so that the same authenticated request was executed more than once. Where a UsernameToken is not bound to the message by a signature, the copies could carry different message bodies. The attacker needs to obtain the message while it is still in transit; a message captured after it has been accepted cannot be replayed. Affects deployments with a replay cache configured, as Apache CXF has by default. The value is now checked and remembered in a single atomic step. Custom ReplayCache implementations should override the new ReplayCache.addIfAbsent method with an operation that is atomic in their underlying store. Users are recommended to upgrade to versions 4.0.3 or 3.0.7 or 2.4.5, which fix this issue.5h
CVE-2026-1254238.8 HIG
—
——0A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so that writing the README followed a symbolic link and overwrote a server-side git hook, which runs commands as the Gitea system user. The initial commit is now built in a freshly initialized directory, and a new repository only becomes ready, and accepts pushes, once its initialization is complete.2h