CVE
taOS: Authenticated Non-Admin Host Code Execution via Skill Runtime
taOS 1.0.0-beta.22 and earlier are affected, where any authenticated non-admin user can run Python code on the host. Fixed in 1.0.0-beta.23.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.0.0-beta.23
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected versions are 1.0.0-beta.22 and earlier. Attacker needs a valid non-admin user session.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Authenticated non-admin users of the taOS self-hosted AI agent OS can run arbitrary Python code on the host by sending a request to the skill execution endpoint, because the endpoint skips admin and ownership checks. The attack is carried out remotely over the network with only a low-privilege login, and the code runs as the taOS backend process user, giving full control of the host.
Read the original description
taOS is a self-hosted AI agent OS. Prior to version 1.0.0-beta.23, the POST /api/skill-exec/{skill_id}/call endpoint in taOS executes built-in skills — including the code_exec skill which runs arbitrary Python via subprocess.run(["python3", "-c", code]) — without performing any admin role check, skill ownership check, or agent assignment verification. Any authenticated non-admin user can supply attacker-controlled Python code in the request body and have it executed as the taOS backend process user on the host, achieving full remote code execution with no privilege escalation required beyond a valid (non-admin) session. This issue has been patched in version 1.0.0-beta.23.
Who should check
Operators running taOS up to 1.0.0-beta.22 where non-admin users hold accounts through admin-issued invites.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected versions are 1.0.0-beta.22 and earlier. Attacker needs a valid non-admin user session.Upgrade to a fixed version: 1.0.0-beta.23.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-67547 (taOS: Authenticated Non-Admin Host Code Execution via Skill Runtime), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-67547 (entry last updated 2026-11-11):
Affected:
- jaylfc taOS: fixed in 1.0.0-beta.23
Fixed versions: 1.0.0-beta.23.
Conditions (all must be true for the bug to be hit):
- Affected versions are 1.0.0-beta.22 and earlier. (source: https://github.com/jaylfc/taOS/security/advisories/GHSA-h24f-gp4c-8qjm)
- Attacker needs a valid non-admin user session. (source: https://github.com/jaylfc/taOS/security/advisories/GHSA-h24f-gp4c-8qjm)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-67547 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-67547 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/jaylfc/taOS/security/advisories/GHSA-h24f-gp4c-8qjm
- https://github.com/jaylfc/taOS/commit/8998d85190424d5e843880b4ca256e79b653a304
- https://github.com/jaylfc/taOS/releases/tag/v1.0.0-beta.23
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-67547
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-67547"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- jaylfc taOS
fixed in 1.0.0-beta.23
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-67547
Is CVE-2026-67547 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Any authenticated non-admin taOS user can supply Python code that the skill runtime runs as the taOS backend process user on the host. That gives full remote code execution on the host.Source: github.com, github.com
Which versions are affected by CVE-2026-67547?
taOS: before 1.0.0-beta.23.Source: cve.now feed data
Am I affected, and how do I check?
Versions 1.0.0-beta.22 and earlier are affected, and the bug requires a valid non-admin user session. To check, look at the taOS version you run and compare it with 1.0.0-beta.22.Source: github.com, github.com
How do I fix CVE-2026-67547?
Update to 1.0.0-beta.23, which the advisory says all users should do. The facts list no workaround.Source: github.com, github.com