CVE-2026-67547

validatingZero is analyzing and reversing it now.

GHSA-h24f-gp4c-8qjm ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
jaylfc taOS < 1.0.0-beta.23
fixed in 1.0.0-beta.23
CWE-862 Missing Authorization
ETK-2026-4227Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

taOS versions before 1.0.0-beta.23 do not enforce authorization checks when invoking built-in skills through a skill-execution API. An authenticated non-admin user can cause attacker-controlled code to run as the taOS backend process user; a valid non-admin session is required.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade taOS to version 1.0.0-beta.23 or later. Restrict access to taOS accounts and the skill-execution API until the upgrade is complete.

fixed in 1.0.0-beta.23

check
building now
exploit
not yet
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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 21:46Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-11 21:46Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-67547

{
  "etk_id": "ETK-2026-4227",
  "cve_id": "CVE-2026-67547",
  "display_id": "CVE-2026-67547",
  "ghsa_id": "GHSA-h24f-gp4c-8qjm",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Authorization bypass enables code execution in taOS",
  "summary": "taOS versions before 1.0.0-beta.23 do not enforce authorization checks when invoking built-in skills through a skill-execution API. An authenticated non-admin user can cause attacker-controlled code to run as the taOS backend process user; a valid non-admin session is required.",
  "mitigation": "Upgrade taOS to version 1.0.0-beta.23 or later. Restrict access to taOS accounts and the skill-execution API until the upgrade is complete.",
  "vendor": "jaylfc",
  "product": "taOS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.0.0-beta.23"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.0.0-beta.23"
      ],
      "package_name": "taOS",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-11T21:46:37.959000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T21:46:37.959000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T21:46:37.959000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-67547"
    }
  }
}

published 2026-11-11 22:57Z
last change 2026-11-11 22:57Z

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.