CVE-2026-77930 EvoScientist 0.1.0 before 0.2.5 Human Approval Bypass via Async Sub-Agents
Critical 9.3
Published
Updated
Check this codebase for CVE-2026-77930 and fix it if it is affected.
What it is: CVE-2026-77930 is a critical vulnerability in EvoScientist, published on 20 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77930 exists.
Affected product: EvoScientist. 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-77930/ (Markdown: https://insights.sbomify.com/CVE-2026-77930/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-77930?
CVE-2026-77930 is a critical vulnerability in EvoScientist, published on 20 Oct 2026.
Official description
EvoScientist 0.1.0 before 0.2.5 contains an approval bypass vulnerability that allows attackers to run host shell commands by delegating them to async sub-agents lacking an interrupt_on gate. Attackers can plant instructions in ingested content such as fetched web pages, so the agent calls start_async_task and runs commands with user privileges and environment secrets.
Weakness: CWE-862
Which versions are affected by CVE-2026-77930?
How do I fix CVE-2026-77930?
No fix has been published for CVE-2026-77930 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-77930 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77930 exists.
Sources
Also known as GHSA-626g-hx6f-fj54.