OmniAgent Bash Approval Gate Bypass via find -execdir in Safe-Command Allowlist
OmniAgent's default deployment is affected through bash calls in the coding and full tool profiles, which go through an approval check that find -execdir can bypass. No fix is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. bash is in the require_approval list for the coding and full tool profiles, so bash calls go through the approval check Applies in a default deployment
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OmniAgent, an AI agent framework, contains a flaw in its safe-command check that treats any find command as harmless without inspecting its -execdir arguments. An attacker who can inject prompts into an agent can reach this remotely without logging in, but it requires a user to take an action, and the attacker could then run tools like dd, nc, perl, or openssl through an unsandboxed shell to overwrite files or execute code without approval.
Read the original description
OmniAgent through commit 12b98c5 contains an approval bypass vulnerability in ReflexionAgent._is_safe_bash_command that treats any command starting with find as safe without inspecting -execdir arguments. Prompt-injected agents can run find with -execdir to invoke binaries like dd, nc, perl or openssl through an unsandboxed shell, overwriting files or executing code without human approval.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.7/10CVSS 7.7
- No patch5/5No patch listed yet
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
bash is in the require_approval list for the coding and full tool profiles, so bash calls go through the approval check Applies in a default deploymentWorkaround: The facts do not describe a workaround. No fix is listed, so the facts provide no guidance on limiting the affected feature.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- YeQing17-2026 OmniAgent
Version range not reported
Evidence 4
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125368
Is CVE-2026-125368 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
OmniAgent's safe-command allowlist lets find run without approval, but find's -execdir option can start other programs such as dd, nc, perl or openssl. Those programs can overwrite files or run code without the human approval step.Source: github.com, vulncheck.com
Am I affected, and how do I check?
The facts list OmniAgent with no version ranges. The approval check covers bash calls in the coding and full tool profiles in a default deployment, so the tool profile setting and whether bash is in the require_approval list are the things to check.Source: github.com, vulncheck.com
How do I fix CVE-2026-125368?
The facts do not name a fixed version or an upgrade target, so no upgrade path is given.Source: github.com, vulncheck.com
What if there's no patch?
The facts do not describe a workaround. No fix is listed, so the facts provide no guidance on limiting the affected feature.Source: github.com, vulncheck.com