opencode fixes unconsented remote code execution flaw

Tier B · Patch this week – Put it in the sprint

Tier B because: Full takeover OR secrets exposed OR supply chain

Reach

Attack

Damage

Fix

Full takeover

What to do

Update opencode to the release that contains the fix

The Brief

opencode fixed a remote code execution (RCE) flaw that ran without user consent.
The source describes the flaw as arising from a 'Refactor'; it gives no version numbers or CVE.

Why it matters

Developers running opencode should update to the fixed release, and the source argues that agent CLIs need browser-style automatic updates for fixes like this to reach users.

The checklist behind the tier

Checklist · 2 of 10 yes · estimated from older data, not yet checked against the sources

Yes	Hits tech teams	Does it affect software, devices or services that developers, ops or IT teams build with, run or are responsible for?
No	Core infrastructure	Is the flaw in, or the compromise of, software that nearly every team runs?
No	Popular tool	Is the flaw in, or the compromise of, a widely used framework, tool, platform, OS or package?
No	Exploited in the wild	Do sources report real attacks using it?
No	Public exploit	Is a working exploit or detailed proof-of-concept public?
No	Remote, no login	Can an attacker use it over the network without credentials or user interaction?
Yes	Full takeover	Does it lead to code execution, root/admin rights or full account takeover?
No	Secrets exposed	Were credentials, tokens, keys, configs, source code or customer data stolen or exposed?
No	Supply chain	Was malicious code shipped through a channel developers trust?
No	No fix yet	Is there no patched version yet?

Source

opencode Fixed a No-Consent RCE in a 'Refactor.' Agent CLIs Need Browser-Style Updates ↗ DEV Community: ai · 3h ago

First seen 3h ago · 1 source · Full story page · How tiers are decided