jaylfc taOS up to 1.0.0-beta.22 Code Execution call subprocess.run privileges management

Summaryinfo

A vulnerability marked as very critical has been reported in jaylfc taOS up to 1.0.0-beta.22. The impacted element is the function subprocess.run of the file /api/skill-exec/{skill_id}/call of the component Code Execution. This manipulation causes privileges management. The identification of this vulnerability is CVE-2026-67547. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as very critical was found in jaylfc taOS up to 1.0.0-beta.22. Affected by this vulnerability is the function subprocess.run of the file /api/skill-exec/{skill_id}/call of the component Code Execution. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-67547 since 07/29/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/11/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 1.0.0-beta.23 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• jaylfc

Name

• taOS

Version

• 1.0.0-beta.0
• 1.0.0-beta.1
• 1.0.0-beta.2
• 1.0.0-beta.3
• 1.0.0-beta.4
• 1.0.0-beta.5
• 1.0.0-beta.6
• 1.0.0-beta.7
• 1.0.0-beta.8
• 1.0.0-beta.9
• 1.0.0-beta.10
• 1.0.0-beta.11
• 1.0.0-beta.12
• 1.0.0-beta.13
• 1.0.0-beta.14
• 1.0.0-beta.15
• 1.0.0-beta.16
• 1.0.0-beta.17
• 1.0.0-beta.18
• 1.0.0-beta.19
• 1.0.0-beta.20
• 1.0.0-beta.21
• 1.0.0-beta.22

Website

• Product: https://github.com/jaylfc/taOS/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion