CVE-2026-125368YeQing17-2026 OmniAgent incomplete denylist
CVE-2026-125368 is a incomplete denylist in YeQing17-2026 OmniAgent, rated high (7.7 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
A list of forbidden inputs misses some, so a variant gets through.
How it is reached
An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker drive the component into behaviour its authors did not intend.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place YeQing17-2026 OmniAgent runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Interfaces that accept external input. The flaw sits at the input boundary of the affected component.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- People who open files and links. Mail, chat and browsers are the delivery path.
- At the input boundary of the affected component. An attacker who crosses it can drive the component into behaviour its authors did not intend.
Questions to answer about your own systems
- Where does YeQing17-2026 OmniAgent run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Issue reports
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.