Summary
A permission-checking flaw in knowns allows the project.set action to bypass authorization guards unconditionally. A read-only agent session may therefore repoint the server to another project directory and gain capabilities that can permit project changes.
Affected context
The issue affects knowns deployments through version 0.33.0 where the project.set action is available to agent sessions and is exempted from normal permission checks. Risk is higher when an attacker can obtain or operate a read-only session and when the server can access additional project directories.
Exploit preconditions
- Attack surface: The knowns agent or server interface exposing the
project.setaction - Required access: A valid read-only agent session or equivalent low-privilege access
- Trigger point: Invocation of
project.setwith a different project directory - Why exploitation is possible: The action is exempted from permission guards, allowing a restricted session to change the server's project context and potentially reach write-capable operations
Why this happens
The underlying bug is an authorization enforcement failure. The project.set operation is treated as an unconditional exception to permission checks rather than being evaluated against the caller's effective privileges. This maps to CWE-863: Incorrect Authorization, where a system fails to properly verify whether a subject is permitted to perform a requested action.
Potential impact
- A read-only session may gain access to project contexts it should not control
- An attacker could modify project files or settings
- Project integrity and data confidentiality could be affected
- Unauthorized project switching could enable further abuse of connected tools
- Shared environments could experience cross-project access or tampering
General mitigation guidance
Mitigation generally focuses on applying authorization checks consistently to every state-changing action, including project-context changes.
Common defensive patterns include:
- Require explicit authorization for changing the active project or project directory
- Apply centralized, deny-by-default permission enforcement to all agent actions
- Validate project identifiers against an allowlist tied to the caller's privileges
- Reduce the filesystem and service permissions available to agent sessions
- Separate read-only browsing capabilities from project-selection and write-capable operations
- Treat project context as security-sensitive state rather than a harmless configuration value
How teams detect issues like this
Organizations can look for:
- Static analysis and code review rules identifying action handlers that bypass shared authorization middleware
- Tests that invoke every state-changing action under read-only, unauthenticated, and cross-project contexts
- Audit events for
project.setcalls, especially those made by low-privilege sessions - Policy enforcement requiring explicit authorization annotations for context-switching operations
- Monitoring for project-directory changes followed by write operations from sessions previously limited to read access
Automated review tools may help identify unconditional permission exemptions and missing authorization tests.

