CVE-2026-67548: taOS: Non-Admin Users Can Access System Settings and Update Actions
taOS is a self-hosted AI agent OS. Prior to version 1.0.0-beta.25, tinyagentos (taOS) registers all system settings routes under a single APIRouter() instance created with no admin authorization dependency. Any authenticated user—including non-admin invited users whose isadmin flag is explicitly False—can read the full system configuration, overwrite it, modify platform settings, trigger a git pull + dependency reinstall + service restart, and switch the tracked update branch. Successful exploitation of the write endpoints causes immediate configuration corruption or a denial of service for all users on the instance from a low-privileged account. This issue has been patched in version 1.0.0-beta.25.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
tinyagentos (taOS)to a version that resolves this vulnerability.Fixed in 1.0.0-beta.25
Event History
Frequently Asked Questions
Who can exploit this issue?
Any authenticated taOS user can exploit it, including invited non-admin users whose is_admin flag is explicitly False. The attacker needs a valid low-privileged account; no user interaction is required.
Are default deployments affected?
Affected versions register all system-settings routes without an admin authorization dependency. Therefore, an affected instance with any non-admin authenticated user is exposed to unauthorized settings access and changes.
What can an attacker do after exploiting the missing authorization?
A non-admin user can read and overwrite the full system configuration, alter platform settings, trigger a git pull with dependency reinstallation and service restart, or change the tracked update branch. Write actions can immediately corrupt configuration or deny service to all instance users.
How can I remediate this vulnerability?
Upgrade taOS to version 1.0.0-beta.25, which patches the issue. If upgrading cannot happen immediately, restrict access so that non-admin authenticated users cannot reach the affected system-settings routes.