← back to feed
ETK-2026-2767Zero's internal tracking ID, independent of the CVE number.

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

waiting for further signalsZero needs more public information before it can validate it.
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.
Tailscale SSH
ETK-2026-2767Zero's internal tracking ID, independent of the CVE number., no cve assigned
3h 26msince last run
1h 21mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −4h18mwaiting for further signals−3h26m
−4h
−3h
−2h
−1h
0

description

Tailscale SSH deployments may be exposed to a privilege-escalation path when tailnet ACLs broadly permit access from authorized devices to servers. An attacker who has compromised an authorized device may be able to use that access to gain elevated privileges on an allowed server.

mitigation

Restrict tailnet ACLs to the smallest necessary source devices, destinations, and SSH access paths, especially for privileged servers. Apply Tailscale updates containing the vendor's fix when they are available; the evidence does not identify a fixed version.

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.
contextual
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
1h 21m
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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-27 14:09Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2767",
  "cve_id": null,
  "display_id": "ETK-2026-2767",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Privilege escalation flaw in Tailscale SSH",
  "summary": "Tailscale SSH deployments may be exposed to a privilege-escalation path when tailnet ACLs broadly permit access from authorized devices to servers. An attacker who has compromised an authorized device may be able to use that access to gain elevated privileges on an allowed server.",
  "mitigation": "Restrict tailnet ACLs to the smallest necessary source devices, destinations, and SSH access paths, especially for privileged servers. Apply Tailscale updates containing the vendor's fix when they are available; the evidence does not identify a fixed version.",
  "vendor": "Tailscale",
  "product": "Tailscale SSH",
  "affected": [],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 80.67644558333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T14:09:46+00:00",
      "days": -0.17922792168981483,
      "is_lower_bound": true,
      "measured_at": "2026-10-27T18:27:51.320545+00:00",
      "url": "https://www.bleepingcomputer.com/news/security/tailscale-warns-of-serious-ssh-flaws-allowing-root-privilege-escalation/"
    }
  }
}

published 2026-10-27 14:25Z
last change 2026-10-27 18:08Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.