Summary
OpenAgents Workspace exposes its workspace-listing endpoint without requiring authentication. An unauthenticated attacker may enumerate workspace details, including identifiers, member information, creator emails, and unmasked browserfabric API keys, when the affected backend is reachable.
OpenAgents Workspace exposes its workspace-listing endpoint without requiring authentication. An unauthenticated attacker may enumerate workspace details, including identifiers, member information, creator emails, and unmasked browserfabric API keys, when the affected backend is reachable.
Affected context
The vulnerability occurs in OpenAgents Workspace backend deployments using the affected launcher component where the GET /v1/workspaces endpoint is accessible without authentication. Risk is higher when the service is network-exposed and workspace settings contain browserfabric API keys or other sensitive metadata.
The vulnerability occurs in OpenAgents Workspace backend deployments using the affected launcher component where the GET /v1/workspaces endpoint is accessible without authentication. Risk is higher when the service is network-exposed and workspace settings contain browserfabric API keys or other sensitive metadata.
Exploit preconditions
- Attack surface: HTTP API endpoint at
GET /v1/workspaces - Required access: No authentication, according to the vulnerability description
- Trigger point: A request to the workspace-listing endpoint
- Why exploitation is possible: The endpoint returns workspace records and settings without first verifying the caller's identity or authorization
- Attack surface: HTTP API endpoint at
GET /v1/workspaces - Required access: No authentication, according to the vulnerability description
- Trigger point: A request to the workspace-listing endpoint
- Why exploitation is possible: The endpoint returns workspace records and settings without first verifying the caller's identity or authorization
Why this happens
The underlying issue is an authentication control failure mapped to CWE-306: Missing Authentication for Critical Function. A sensitive workspace-listing operation is exposed without a mandatory identity check, allowing anonymous callers to retrieve data that should be restricted to authorized users. Returning unmasked secrets in the response further increases the impact of the missing access control.
The underlying issue is an authentication control failure mapped to CWE-306: Missing Authentication for Critical Function. A sensitive workspace-listing operation is exposed without a mandatory identity check, allowing anonymous callers to retrieve data that should be restricted to authorized users. Returning unmasked secrets in the response further increases the impact of the missing access control.
Potential impact
- An attacker may enumerate workspace IDs and slugs
- An attacker may obtain creator email addresses and member lists
- Exposed API keys could be reused to access connected services or perform actions under the associated identity
- Workspace metadata may support targeted phishing, reconnaissance, or subsequent attacks
- An attacker may enumerate workspace IDs and slugs
- An attacker may obtain creator email addresses and member lists
- Exposed API keys could be reused to access connected services or perform actions under the associated identity
- Workspace metadata may support targeted phishing, reconnaissance, or subsequent attacks
General mitigation guidance
Mitigation typically focuses on enforcing authentication and authorization at every sensitive API boundary.
Common defensive patterns include:
- Require authenticated identity verification before serving workspace listings
- Enforce tenant- and workspace-level authorization checks
- Return only the minimum fields needed by the requesting client
- Never expose API keys or other secrets in ordinary workspace responses; use secret references or redacted values instead
- Rotate credentials that may have been exposed and apply least-privilege permissions to them
- Deny access by default and protect administrative endpoints through centralized policy enforcement
Mitigation typically focuses on enforcing authentication and authorization at every sensitive API boundary.
Common defensive patterns include:
- Require authenticated identity verification before serving workspace listings
- Enforce tenant- and workspace-level authorization checks
- Return only the minimum fields needed by the requesting client
- Never expose API keys or other secrets in ordinary workspace responses; use secret references or redacted values instead
- Rotate credentials that may have been exposed and apply least-privilege permissions to them
- Deny access by default and protect administrative endpoints through centralized policy enforcement
How teams detect issues like this
Organizations commonly detect missing authentication and excessive data exposure through:
- API inventory reviews that identify sensitive endpoints lacking authentication middleware
- Static and semantic analysis for routes that return workspace or credential data without identity checks
- Code review signals such as unauthenticated handlers, missing authorization decorators, and direct serialization of settings maps
- Dynamic testing that requests sensitive endpoints without credentials and verifies that access is denied
- API gateway or policy rules requiring authentication for workspace and administrative route groups
Organizations commonly detect missing authentication and excessive data exposure through:
- API inventory reviews that identify sensitive endpoints lacking authentication middleware
- Static and semantic analysis for routes that return workspace or credential data without identity checks
- Code review signals such as unauthenticated handlers, missing authorization decorators, and direct serialization of settings maps
- Dynamic testing that requests sensitive endpoints without credentials and verifies that access is denied
- API gateway or policy rules requiring authentication for workspace and administrative route groups
