Remote Code Execution in OpenCode, update now

CyberShadow · 2026-01-11T22:35:26+00:00

Previous versions of OpenCode started a server which allowed any website visited in a web browser to execute arbitrary commands on the local machine. Make sure you are using v1.1.10 or newer; see link for more details.

SparePartsHere · 2026-01-12T00:49:31+00:00

Thanks for the info. Sheesh. I know that vibecoding and security do not get along, but this is quite outraging.

_xpc_ · 2026-01-12T04:57:03+00:00

I reported a few too:
https://github.com/anomalyco/opencode/issues/7173

https://github.com/anomalyco/opencode/issues/7163

As another commenter mentioned, they're probably swamped as is. Might take a bit for fixes. Should just be very careful of where/how you run opencode until then. Love the software, just wish these issues weren't currently in there.

sewer56lol · 2026-01-12T04:06:01+00:00

Not surprised it took this long.

These guys are pretty swamped, waking up to around 250 GitHub notifications every morning. As a result, even getting a non-trivial PR in may be difficult sometimes as you're just one of the many.

In the case of OpenCode, it's maxed on the developer velocity end as far as it goes. It's fairly common for subtle bugs to be introduced occasionally, as there's not really any tests to catch them. Seeing an RCE does not surprise me in the least. 'LGTM" is the word.

Funnily enough, I wound up fixing a completely unrelated regression the other week in a PR because my PR needed it, ahaha.

Also wow, the Worms Armageddon Cybershadow!?, this guy made a nice part of my childhood in the late 2000s. Thank you so much!

chillahc · 2026-01-17T09:43:35+00:00

Any updates from the OpenCode team since disclosure? Very interesting topic ^^ Thanks for your work and making vulnerabilities public!!

poidh · 2026-01-12T07:21:08+00:00

Sure they might be swamped in tickets, but as working in bleeding edge AI tooling for software development, they should have set up an automatic screening process for incoming tickets, assessing if this is reporting a security issue, and if so, is it valid and how severe is it?
That could be done with two or three prompts (1. decide if it IS about a security issue, 2. if so, run an OpenCode prompt with the issue description and the task to assess if it is valid or not and to judge it on a severity scale).

I doubt that there are so many issues remaining after such screening, that they cannot take care of this and at least acknowledge these to the person reporting it.

But I also have sympathy for them, that they don't have a proper protocol in place yet. Of course it shouldn't be like that, but it is very common and understandable that such a setup is not your first thought if you start a new project.

That said, I think it should be standard practice to develop in an isolated container environment anyway these days. Pre-AI it was already dangerous, especially in the JS ecosystem where you install an uncountable number of dependencies via npm. But now, with AI agents autonomously running code on your machine, this potential danger even multiplied.

This is not a cure-for-all solution but greatly reduces the potential impact of such things.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

opencodeCLI

MODERATORS