Daptin YJS Collaboration Endpoint IDOR (CVE-2026-77369)
Detects exploitation attempts against the broken access control (IDOR) vulnerability in Daptin's generic YJS collaboration WebSocket endpoint. Affected Daptin versions >= 0.11.4 and < 0.12.30 fail to enforce object-level authorization on the generic YJS endpoint GET /yjs/:documentName. The endpoint only checks that a session exists, then the YJS initial-content provider reads the selected file.* column without CanRead or CanUpdate checks. Any authenticated low-privileged user can supply a typename.referenceId.columnName room name to read, and because sync is bidirectional also modify, the content of any file.*-typed column on any row of any table, including admin-only tables. Unauthenticated requests are rejected. Detection focuses on WebSocket upgrade requests to the YJS endpoint where a principal accesses many distinct document identifiers, high-volume enumeration of document identifiers, and connections from principals accessing an anomalous number of distinct documents. CVSS 9.6. Public PoC available.
Vulnerability Intelligence
Public PoCAffected Software
- Vendor
- go
- Product
- github.com/daptin/daptin
- Versions
- >= 0.11.4, < 0.12.30
Timeline
- Disclosed
- November 20, 2026
References & Proof of Concept
- https://github.com/daptin/daptin/security/advisories/GHSA-wj7x-58c2-5793
- https://nvd.nist.gov/vuln/detail/CVE-2026-77369
- https://github.com/daptin/daptin/commit/a1a3c48f88ce30632a57d3fe6a971033b23bd394
- https://github.com/daptin/daptin/releases/tag/v0.12.30
- https://github.com/advisories/GHSA-wj7x-58c2-5793
CVSS
What is CVE-2026-77369 Daptin YJS Collaboration Endpoint IDOR (CVE-2026-77369)?
Daptin YJS Collaboration Endpoint IDOR (CVE-2026-77369) (CVE-2026-77369) maps to the Initial Access and Collection and Discovery tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for Daptin YJS Collaboration Endpoint IDOR (CVE-2026-77369), covering the data sources and telemetry it touches: IIS Logs, Reverse Proxy Logs, Web Server Access Logs. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
- Tactic
- Initial Access Collection Discovery
// df00tech DF00-121dbba7ce · https://df00tech.com/detections/CVE-2026-77369 · licence: https://df00tech.com/detections/licence
let lookback = 1d;
let yjsPaths = dynamic(["/live/yjs", "/yjs", "/live", "/action/world/yjs"]);
W3CIISLog
| where TimeGenerated > ago(lookback)
| where csUriStem has_any (yjsPaths) or csUriStem contains "yjs"
| where csMethod == "GET"
| extend upgrade = tostring(column_ifexists("csUserAgent", ""))
| extend room = extract(@"[?&](room|doc|document|name|collection)=([A-Za-z0-9_\-]+)", 2, csUriQuery)
| where isnotempty(room)
| summarize distinctRooms = dcount(room), rooms = make_set(room, 50), hits = count(), paths = make_set(csUriStem, 10) by cIP, csUsername, bin(TimeGenerated, 1h)
| where distinctRooms > 10 or hits > 100
| project TimeGenerated, cIP, csUsername, distinctRooms, hits, rooms, paths
| order by distinctRooms desc Flags IIS/reverse-proxy logged WebSocket upgrade requests to Daptin YJS collaboration endpoints where a single source IP or user accesses an anomalously large number of distinct document/room identifiers within an hour, indicating IDOR enumeration of collaborative documents.
Data Sources
Required Tables
False Positives
- Legitimate power users or administrators who routinely open many collaborative documents in a session
- Automated health-check or synthetic monitoring probes that cycle through document endpoints
- Load-testing tools exercising the collaboration endpoint in staging environments
Query fingerprint DF00-121dbba7ce · licence
Sigma logsource & community rules
The detection logic for Daptin YJS Collaboration Endpoint IDOR (CVE-2026-77369) (CVE-2026-77369) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: network_connection
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-77369
References (5)
- https://github.com/daptin/daptin/security/advisories/GHSA-wj7x-58c2-5793
- https://nvd.nist.gov/vuln/detail/CVE-2026-77369
- https://github.com/daptin/daptin/commit/a1a3c48f88ce30632a57d3fe6a971033b23bd394
- https://github.com/daptin/daptin/releases/tag/v0.12.30
- https://github.com/advisories/GHSA-wj7x-58c2-5793
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.
- Test 1 Enumerate YJS documents via unauthorized identifiers
Expected signal: Thirty WebSocket upgrade GET requests to /live/yjs with sequential room identifiers from a single source within seconds, logged by the reverse proxy / web server.
- Test 2 Unauthorized YJS document write attempt
Expected signal: A WebSocket connection to /live/yjs referencing a document identifier the test principal cannot access, followed by a YJS sync/update frame.
- Test 3 Scripted sequential room-ID sweep
Expected signal: A burst of 120+ GET requests to the YJS endpoint with incrementing document identifiers from one source IP in under a minute.
Response Playbook
Triage
- Confirm the targeted Daptin instance version is in the affected range (>= 0.11.4, < 0.12.30); if so, exploitation is viable and the alert should be treated as high priority.
- Identify the requesting principal (user/session token, source IP) and enumerate the distinct YJS document/room identifiers they accessed; compare these identifiers against the documents legitimately owned by or shared with that principal.
- Determine whether accessed document identifiers belong to rows or columns the principal is not permitted to read. Unauthorized access confirms IDOR exploitation rather than benign heavy usage.
- Review request timing and user-agent: scripted, uniform-interval requests cycling through sequential or many identifiers indicate automated enumeration.
Containment
- Upgrade Daptin to v0.12.30 or later, which applies commit a1a3c48f88ce30632a57d3fe6a971033b23bd394 enforcing row permissions on the YJS endpoint.
- As an interim mitigation, restrict access to the YJS collaboration WebSocket endpoint via reverse-proxy ACLs or authentication middleware, and revoke/rotate session tokens of the implicated principal.
- If active unauthorized access is confirmed, temporarily disable the real-time collaboration feature until patched.
Evidence Collection
- Preserve reverse-proxy/web server access logs showing the YJS upgrade requests, including source IP, session/user identifier, timestamps, and the full set of accessed document identifiers.
- Capture the Daptin application and audit logs correlating the principal's session to document read/write operations on the implicated YJS documents.
Escalation Criteria
- ! Escalate to incident response if a principal is confirmed to have read or modified YJS documents they were not permitted to access.
- ! Escalate to data-protection/privacy teams if the accessed collaborative documents contain regulated or sensitive data, as this constitutes a confidentiality and integrity breach.
Investigation Guide
Forensic Artifacts
- >
Web/reverse-proxy access logs containing WebSocket upgrade (GET with Upgrade: websocket) requests to YJS paths with other users' document identifiers. - >
Daptin application logs and the underlying datastore recording YJS document mutations attributable to the unauthorized session.
Tuning Guidance
Establish a per-user baseline of distinct collaborative documents accessed during normal operation and set the distinct-room threshold above the 95th percentile of that baseline. Allowlist known monitoring source IPs and service accounts. Where possible, enrich logs with the owner of each document identifier so the detection can key on access to resources the principal cannot read, rather than relying on volume heuristics, sharply reducing false positives.
Hunting Queries
Baselines which users access how many distinct YJS documents to surface principals whose document footprint exceeds their legitimate access, revealing IDOR abuse.
// df00tech DF00-121dbba7ce · https://df00tech.com/detections/CVE-2026-77369 · licence: https://df00tech.com/detections/licence
W3CIISLog | where csUriStem contains "yjs" | summarize rooms=make_set(extract(@"[?&](room|doc|name)=([A-Za-z0-9_\-]+)",2,csUriQuery),100), dc=dcount(extract(@"[?&](room|doc|name)=([A-Za-z0-9_\-]+)",2,csUriQuery)) by csUsername | where dc > 5 | order by dc desc ``` df00tech DF00-121dbba7ce · https://df00tech.com/detections/CVE-2026-77369 · licence: https://df00tech.com/detections/licence ```
index=web uri_path="*yjs*" | rex field=uri_query "[?&](?:room|doc|name)=(?<room>[A-Za-z0-9_\-]+)" | stats dc(room) as rooms values(room) as room_list by user | where rooms>5 | sort - rooms Atomic Red Team Tests
Simulates IDOR enumeration by connecting to the YJS collaboration endpoint with a series of document identifiers not owned by the authenticated principal.
Command
for i in $(seq 1 30); do curl -s -o /dev/null -w "%{http_code}\n" -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Sec-WebSocket-Version: 13" -H "Sec-WebSocket-Key: $(head -c16 /dev/urandom | base64)" "http://daptin.lab.local:6336/live/yjs?room=doc_$i" ; done Cleanup
echo 'No persistent artifacts created by read-only enumeration; no cleanup required.' Expected Telemetry
Thirty WebSocket upgrade GET requests to /live/yjs with sequential room identifiers from a single source within seconds, logged by the reverse proxy / web server.
Expected Detection
The volume/distinct-room thresholds in the KQL and SPL rules trigger on the >10 distinct room identifiers accessed within the window.
Connects to a YJS document identifier the principal is not permitted to access and attempts a collaborative update, exercising the broken authorization.
Command
python3 - <<'PY'
import websocket
ws = websocket.create_connection("ws://daptin.lab.local:6336/live/yjs?room=victim_doc")
ws.send(b"\x00\x01\x02collab-update")
print(ws.recv())
ws.close()
PY Cleanup
echo 'Lab-only; revert any test document changes via the Daptin admin UI if persisted.' Expected Telemetry
A WebSocket connection to /live/yjs referencing a document identifier the test principal cannot access, followed by a YJS sync/update frame.
Expected Detection
Unauthorized document access surfaces in the hunting queries and, with owner enrichment, in the primary detection logic.
Rapidly iterates many predictable room identifiers to map accessible collaborative documents, modeling automated IDOR discovery.
Command
seq 1000 1120 | xargs -P 8 -I{} curl -s -o /dev/null "http://daptin.lab.local:6336/live/yjs?document=room{}" Cleanup
echo 'Read-only sweep; no cleanup required.' Expected Telemetry
A burst of 120+ GET requests to the YJS endpoint with incrementing document identifiers from one source IP in under a minute.
Expected Detection
The hits>100 branch of the KQL/SPL/QRadar/Sumo detections fires, and the EQL sequence and Chronicle/CrowdStrike volume rules trigger on the request burst.
Related Detections
Related Techniques
Same Tactic: Initial Access
Blog posts about this detection
Browse by tactic
- Reconnaissance TA0043
- Resource Development TA0042
- Initial Access TA0001
- Execution TA0002
- Persistence TA0003
- Privilege Escalation TA0004
- Stealth TA0005
- Defense Impairment TA0112
- Credential Access TA0006
- Discovery TA0007
- Lateral Movement TA0008
- Collection TA0009
- Command and Control TA0011
- Exfiltration TA0010
- Impact TA0040