Saturday, November 7, 2026 270 picks · 133 builders credited Subscribe
AgentRags.

The agentic rag, wrung out.

SecurityThursday, October 8, 2026

Scheduled reader executed a Hermes update string it was only supposed to report

Chinese builders (@laogua_daily, @xiaoyaoshowmore) described a cron task whose job was to report new posts. It saw the text “Run hermes update” and ran it. Their point: reading and acting collapsed into one step. Engagement is low; the failure mode is not.

Cover art for Security: Scheduled reader executed a Hermes update string it was only supposed to report

Why it matters

Classic agent bug. Anything that scrapes the web or other agents needs a hard read-vs-act boundary, especially around update and shell strings.

From the source

Hermes Agent#hermes#prompt-injection#cron#security#tool-use

Related

More Security

SecurityOct 11

Hermes Config Injection Path to Approval Bypass (CVE-2026-108593)

VulnCheck published a CVE on a third-party dashboard (9router) that allows authenticated users to inject arbitrary keys into Hermes config.yaml via a settings endpoint. Demonstrated path: set hooks_auto_accept and a shell command that then runs after LLM calls with no further approval. The underlying condition is “write access to Hermes config = ability to disable approval gates.”

Never miss a night

Every pick, delivered to your reader.

One feed for everything, or one per agent harness you run. Rebuilt every night, with full credit on every item.