CVE-2026-109437: Cognition < 0.13.0 Unauthenticated RCE via Local Shell Backend

Published Oct 19, 2026
·
Updated

Cognition before 0.13.0 contains an unauthenticated remote code execution vulnerability due to defaulting its agent sandbox backend to local execution and shipping no authentication on its REST/SSE API. Attackers can create a session via POST /sessions and post a message via POST /sessions/{id}/messages without credentials, causing the Deep Agents ReAct loop to run attacker-directed shell commands through the local shell backend, resulting in remote code execution as the server process.

Affected Software

1 affected component
Cognition Cognition<0.13.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Cognition to a version that resolves this vulnerability.

    Fixed in 0.13.0
  2. Configuration

    Keep COGNITION_ALLOW_UNSAFE_LOCAL_EXECUTION set to false or unset; do not explicitly set it to true.

    Cognition local sandbox backend COGNITION_ALLOW_UNSAFE_LOCAL_EXECUTION = false

Event History

Oct 19, 2026
CVE Published
via MITRE·06:22 PM
Data Sourced
via MITRE·06:22 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Cognition deployments running a version before 0.13.0 are exposed when their REST/SSE API is reachable by an attacker. The vulnerable configuration uses the local execution backend by default and provides no API authentication.

2

What does an attacker need to exploit this issue?

No credentials or user interaction are required. An attacker can create a session through POST /sessions and submit a message through POST /sessions/{id}/messages to direct shell commands through the agent loop.

3

What level of access could successful exploitation provide?

Successful exploitation executes attacker-directed shell commands as the Cognition server process. This can compromise the confidentiality, integrity, and availability of resources accessible to that process.

4

How can I determine whether my instance is affected?

Verify whether the deployed Cognition version is earlier than 0.13.0 and whether its REST/SSE API accepts session creation and message submission without credentials. Instances using the default local shell backend meet the vulnerable condition described.

5

What should be prioritized for remediation?

Upgrade Cognition to version 0.13.0 or later. Until upgrading is possible, prevent untrusted network access to the REST/SSE API, since the affected API endpoints do not require credentials.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203