CVE Tools

CVE-2026-77930

EvoScientist 0.1.0 before 0.2.5 Human Approval Bypass via Async Sub-Agents

No known exploitation. EPSS puts it in the 52nd percentile. Fixed in 0.2.5.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • EvoScientistAffected: ≥ 0.1.0, < 0.2.5Upgrade to: 0.2.5Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which version of EvoScientist you are running (0.1.0 up to but not including 0.2.5 is affected).
  2. Stop using EvoScientist for any task that fetches or processes untrusted web content until you upgrade.
  3. Upgrade to EvoScientist 0.2.5 or later immediately.
  4. Review any environment secrets or credentials the agent had access to and rotate them if you cannot confirm the agent was safe.
  5. After upgrading, confirm that async sub-agent tasks now require human approval before running shell commands.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

EvoScientist, an AI agent tool, had a flaw that let an attacker sneak hidden instructions into content it reads online and trick it into running commands on your computer without asking for approval first — if you use it, update it now.

CWE-862 (missing authorization) in EvoScientist before 0.2.5 lets prompt-injected content delegate shell execution to async sub-agents that bypass the interrupt_on human-approval gate, yielding unauthenticated remote code execution with the host user's privileges and secrets.

If you're affected

  • Full system takeover
  • Theft of stored secrets/credentials
  • Unauthorized command execution
  • Data loss or tampering

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS52nd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.7% chance of exploitation activity in the next 30 days, which ranks it in the 52nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Sustained, driven by wide press coverage.

Lifecycle

7 events over 2 days, from the signal feeds we watch.

  1. Record updated
  2. Publishedweakness classified, att&ck mapped, record updated, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for EvoScientist, not every advisory.