Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPlant crafted instructions in alert/Slack source
-
DeliveryAgent triages and ingests injected prompt
-
ExploitHeadless execution_allowed() returns True, gate bypassed
-
Executionshell_run executes command on host
-
ImpactExfiltrate LLM, Slack and cloud credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The specific precondition is deployment of OpenSRE using the headless presenter (the subprocess_presenter path) whose execution_allowed() unconditionally returns True, which removes the human confirmation step before shell_run commands. The attacker must additionally be able to place crafted instructions into a source the agent triages - an alert feed or a Slack channel routed through the gateway dispatcher. Exploitation is limited to versions through 0.1.2026.10.19 and to this headless/non-interactive mode; deployments that keep an interactive approval presenter (one that actually enforces confirmation) are not in the always-True code path. Per CVSS no authentication or user interaction is required once a malicious message reaches the triaged channel, but the practical limiting factor is the attacker's ability to inject content into that monitored source. |
| Impact | Signals pull in two directions and must be weighed together. The CVSS 4.0 base vector (AV:N/AC:L/AT:N/PR:N/UI:N with VC:H/VI:H/VA:H) and the SSVC decision (Exploitation: poc, Automatable: yes, Technical Impact: total) describe a high-severity, low-friction flaw: a prompt-injected instruction reaching the agent leads to unconfirmed shell execution and full credential compromise, and the vuln.today Decision label is act_now. Against that, the market-level exploitation signal is modest: EPSS is only 0.45% (38th percentile), the product is not in CISA KEV, and the only exploit artifact is a reference, not verified working exploit code. The act_now urgency is therefore driven by intrinsic impact and automatability rather than by observed mass exploitation - treat it as a priority to patch, but note that low EPSS plus a niche product footprint argue for targeted rather than widespread opportunistic exploitation. No signals directly contradict each other, but the gap between critical severity/act_now and low EPSS/no-KEV should be read as 'serious but not yet demonstrably mass-exploited'; the fixed-version gap (see confidence notes) is the main open risk factor for defenders. |
| Exploit ScenarioDerived | An attacker who can influence a monitored data source - e.g. an alerting pipeline or a Slack channel the OpenSRE agent triages - plants crafted instructions that the LLM agent interprets as a task to run a shell_run command. Because the headless presenter's execution_allowed() unconditionally returns True, the approval gate is skipped and the command runs on the host, enabling exfiltration of LLM, Slack and cloud credentials. A public PoC reference exists (Lasso/VulnCheck); it is not verified as working exploit code, and exploitation needs no authentication or user interaction per the CVSS vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 22, 2026
Missing authorization in OpenSRE through 0.1.2026.10.19 allows remote attackers to run shell commands on the agent host without any human confirmation, because the headless presenter's execution_allowed() returns True unconditionally for every shell_run request. The practical attack path is prompt injection: crafted instructions placed in an alert feed or Slack message that the agent triages get interpreted as commands, letting the attacker execute on the host and exfiltrate LLM, Slack and cloud credentials. No CISA KEV entry exists and EPSS is low at 0.45% (38th percentile), but SSVC rates exploitation proof-of-concept, automatable and total technical impact, and a public PoC reference exists that is not verified as working exploit code; the priority label is act_now.
Earlier versions of this analysis (1)
Headless OpenSRE deployments through 0.1.2026.10.19 allow remote unauthenticated attackers to bypass the shell_run approval gate by injecting instructions into alerts or Slack messages that the agent triages, resulting in host command execution and possible exfiltration of LLM, Slack, and cloud credentials. Publicly available exploit code exists, and this is a genuine high-priority risk for organizations running OpenSRE in headless mode with shell execution enabled; interactive deployments that still enforce the approval prompt are not affected.
RemediationAI
No vendor-released patch or fixed version is identified in the available data at time of analysis, so the controlling measure is to remove the always-True approval path: do not run OpenSRE in headless mode, or apply the upstream code change so execution_allowed() actually enforces confirmation before any shell_run is dispatched, and verify that enforcement on the deployed build. Because the trigger requires attacker-supplied content to reach the triage loop, restrict who can post to Slack channels and alert feeds the agent monitors and validate those sources, accepting that this narrows but does not eliminate injection routes. If shell execution is not essential to the workflow, removing the agent's shell_run capability eliminates the impact but reduces agent functionality. If the agent has been running headless against externally writable channels, treat LLM, Slack and cloud credentials available to the host as potentially exposed and rotate them, noting the operational disruption of token rotation. Track vendor guidance via the VulnCheck advisory at https://www.vulncheck.com/advisories/opensre-through-0.1.2026.10.19-approval-gate-bypass-via-shell-run-prompt-injection and NVD at https://nvd.nist.gov/vuln/detail/CVE-2026-109444.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-862 (Missing Authorization) rooted in the agent's approval gate design. OpenSRE routes shell execution through a presenter abstraction: in the headless presenter implemented in tools/interactive_shell/subprocess_presenter.py, execution_allowed() is hard-coded to return True, so the confirmation step that the interactive presenter performs is silently skipped. The second half of the chain is the ingestion path in gateway/transports/slack/processing/dispatcher.py, which feeds alert and Slack content into the agent's triage loop; because that content is treated as instructions, an attacker who can post into a monitored source obtains prompt injection into an agent holding shell privileges. The assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects that once a malicious message reaches the triaged channel no authentication or user interaction is needed. The exploitability is conditional on deployment mode: only headless, non-interactive installs land in the always-True code path, while an interactive approval presenter that actually enforces confirmation is not affected.
Know when Opensre gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Injection via network-reachable alert/Slack sources triaged autonomously gives AV:N/AC:L/PR:N/UI:N; host command execution and credential theft yield C:H/I:H/A:H within the agent's own authority (S:U).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4DescriptionCVE.org
OpenSRE through 0.1.2026.10.19 contains an approval gate bypass vulnerability that allows attackers to execute shell_run commands without confirmation because the headless presenter's execution_allowed() always returns True. Attackers can inject instructions into alerts or Slack messages triaged by the agent to run commands on the host and exfiltrate LLM, Slack and cloud credentials.
Technical POC Analysis
CWE-862 (Missing Authorization).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
CVE-2026-109444 in OpenSRE, an AI-driven security response agent, allows unauthenticated remote attackers to execute shell commands on the agent host with no human confirmation, enabling theft of LLM, Slack, and cloud credentials. Because OpenSRE often holds privileged access to alerting and collaboration platforms, compromise could cascade into broader cloud and communication-channel exposure. Leadership should treat this as a high-priority risk requiring immediate containment until a patch is released.
Disable the headless presenter's shell execution capability and enforce human confirmation for all shell_run requests; restrict OpenSRE network access to trusted sources; rotate credentials stored or accessible on the agent host; monitor for anomalous command execution and credential access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-104684
GHSA-fqh3-76w5-5vvf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB