# CVE-2026-109444: OpenSRE through 0.1.2026.10.19 Approval Gate Bypass via shell_run Prompt Injection


- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-fqh3-76w5-5vvf

## What is CVE-2026-109444?

CVE-2026-109444 is a critical vulnerability in Tracer-Cloud opensre, published on 20 Oct 2026. 

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-109444?


## How do I fix CVE-2026-109444?

No fix has been published for CVE-2026-109444 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109444 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109444 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109444 and fix it if it is affected.

What it is: CVE-2026-109444 is a critical vulnerability in Tracer-Cloud opensre, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109444 exists.

Affected product: Tracer-Cloud opensre. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109444/ (Markdown: https://insights.sbomify.com/CVE-2026-109444/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109444
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109444
- OSV: https://osv.dev/vulnerability/CVE-2026-109444

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109444/
Summaries are generated and may contain mistakes; the official description above is the record.