CVE-2026-108739 openagents-org CVE debrief

Who should care

Defenders responsible for OpenAgents Workspace installations should assess exposure and prioritize verification of /v1/workspaces endpoint access. This includes reviewing the vulnerability's impact on managed environments, verifying affected scope, and planning vendor-supported updates or mitigations. Security teams and operators should also review compensating controls and monitor for unauthorized access to workspace settings.

Why it matters

CVE-2026-108739 is an information disclosure vulnerability in OpenAgents Workspace backend through launcher-v1.0.17, allowing unauthenticated attackers to list all workspaces and read unmasked browserfabric_api_key. Defenders should prioritize verifying exposure and restricting access to /v1/workspaces endpoint.

• Unauthenticated access to workspace settings
• Potential exposure of browserfabric_api_key
• Increased risk of credential compromise
• Need for verification of endpoint access controls

Technical summary

The OpenAgents Workspace backend through launcher-v1.0.17 contains an information disclosure vulnerability that allows unauthenticated attackers to list all workspaces via GET /v1/workspaces. Attackers can read the unmasked browserfabric_api_key in each workspace's settings map, along with workspace ids, slugs, creator emails and member lists. This vulnerability affects OpenAgents Workspace installations and may lead to potential credential exposure and increased risk of credential compromise. Defenders should prioritize verifying exposure and restricting access to /v1/workspaces endpoint.

Defensive priority

Defenders should prioritize verifying exposure of OpenAgents Workspace installations to unauthenticated credential exposure via /v1/workspaces.

Recommended defensive actions

• Verify OpenAgents Workspace installations for exposure to unauthenticated credential exposure via /v1/workspaces
• Restrict access to /v1/workspaces endpoint
• Monitor for unauthorized access to workspace settings
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. Evidence is limited to public CVE Program records and supplemental sources. Defenders should verify the vulnerability's existence and impact through official channels and assess potential exposure based on provided information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.