ETK-2026-4169Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-c6p8-h5mq-8rr2 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
other:edumeet-room-server <= 4.2-20261109-stable
fixed in 4.2-20261111-stable
CWE-284 Improper Access Control
ETK-2026-4169Zero's internal tracking ID, independent of the CVE number., no cve assigned
cvss9.0ethiack provisional
40msince last run
58mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −3h51mwaiting for further signals−0h40m
−3h
−2h
−1h
0

description

edumeet-room-server before 4.2-20261111-stable can mishandle reconnects and room lifecycle state, allowing isolation between rooms to fail. An unauthenticated attacker who knows an active room name may access room data, and under reconnect-related conditions may gain privileges or bypass meeting access checks.

mitigation

Upgrade edumeet-room-server to 4.2-20261111-stable or later.

fixed in 4.2-20261111-stable

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
58m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-11 10:04Z

this entry in the feed

GET /api/v1/feed/ETK-2026-4169

{
  "etk_id": "ETK-2026-4169",
  "cve_id": null,
  "display_id": "ETK-2026-4169",
  "ghsa_id": "GHSA-c6p8-h5mq-8rr2",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cross-room authorization bypass in edumeet-room-server",
  "summary": "edumeet-room-server before 4.2-20261111-stable can mishandle reconnects and room lifecycle state, allowing isolation between rooms to fail. An unauthenticated attacker who knows an active room name may access room data, and under reconnect-related conditions may gain privileges or bypass meeting access checks.",
  "mitigation": "Upgrade edumeet-room-server to 4.2-20261111-stable or later.",
  "vendor": "other",
  "product": "other:edumeet-room-server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 4.2-20261109-stable"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "4.2-20261111-stable"
      ],
      "package_name": "edumeet-room-server",
      "purl": null
    }
  ],
  "cwes": [
    284
  ],
  "cvss_score": 9,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 58.38551258333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T10:04:06+00:00",
      "days": -0.16038656924768518,
      "is_lower_bound": true,
      "measured_at": "2026-11-11T13:55:03.573542+00:00",
      "url": "https://github.com/edumeet/edumeet-room-server/security/advisories/GHSA-c6p8-h5mq-8rr2"
    }
  }
}

published 2026-11-11 12:27Z
last change 2026-11-11 13:32Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.