RagLeap
Blog

v0.13.4: security fixes after an outside assessment (approvals run once, file actions always need approval, chat approvals only from a private chat)

ragleap-core v0.13.4 was published on 2026-11-17. It contains security fixes that follow an outside assessment by Aleksei Musienko (AMQIC), and groundwork for sub-agents that is off by default. Upgrading switches nothing new on. Source: the v0.13.4 release notes, checked on 2026-11-17.

What was the outside assessment?

In November 2026 Aleksei Musienko of AMQIC (assessment powered by CERNOTIS) sent us a written assessment of ragleap-core. It was a static review of the code. We checked each finding ourselves in the code before acting on it, and the release notes list the ones we confirmed and fixed. He is named here with his agreement. It is not a certification, and it is not the outside review of file writing that has not happened yet (#800).

What was fixed in v0.13.4?

  • An approval runs only once (#1444). Two answers to the same pending action at the same moment (dashboard, API or chat) could both run it, or an approve and a reject could both win. The pending action is now claimed in one atomic step, and the second caller gets "already processed" (F-CORE-005).
  • File actions always need approval (#1445). In full autonomy mode, POST /autonomy/execute took the action label and the channel separately, so a harmless label with a file channel skipped the forced approval. Forced approval now covers both, and a label and channel that do not belong together are refused with 400. Agents were not affected, because their channel comes from the tool table (F-CORE-004).
  • Approvals are accepted only from a private chat (#1447). In a Telegram group or a Discord server channel, everyone in it looked like the owner. An approval typed there is now ignored, and saving a Telegram group id as the approval target is refused (F-CORE-006).
  • Update backups stay out of the image build, and Redis credentials stay out of the log (#1446). .dockerignore lists backups/, and the Redis URL is logged without its user and password (INFRA-F-001, F-CORE-001).

Where does RagLeap accept approvals in chat now?

Approvals (YES <id> or NO <id>) count only when they come from a private, one-to-one conversation with the owner. For Telegram the approval target must be a private chat with the owner (a positive number); a group, supergroup or channel id (a negative number) is not accepted when you save the setting. For Discord, use a direct message conversation. The reason is that in a group the id that arrives belongs to the group, so everyone in it would look like the owner. Approvals from the dashboard or the API are not affected. The guide is docs/approval-chats.md.

What changed for sub-agents?

Sub-agents are off by default and need SUBAGENTS_ENABLED=true. v0.13.4 adds a run tree with cancel (#1418), a delegate tool with limits (#1424), and a Runs tab that shows sub-agent runs and a Cancel run button (#1427). The limits are 3 children per run, 2 at the same time, one level deep, with shared token caps. So far this is tested only with scripted models, not with a real model.

What should I know before upgrading?

  • One additive schema change: db/schema.sql adds four columns and one allowed status (cancelled) to agent_runs. It is safe to run twice. If you run your own database, apply the new block (it starts at the comment "A run can have child runs") before you restart the app.
  • No new setting you must set. File writing, deleting and sub-agents stay off.

What is not tested or not covered?

  • Not tested yet: a real Telegram or Discord group, separate app processes, and sub-agents with a real model.
  • The outside security review of file writing (#800) has not happened. Keep file writing off in production.
  • This release covers the findings listed above. It does not claim that every item of the assessment is closed.
  • Nothing here makes an installation secure, compliant or certified. It helps an operator keep approvals with one person and with one run.

Who do we thank?

Thanks to Aleksei Musienko, Chief Scientist & Founder of AMQIC (MSEC), QIAIMP Scientist, Q-Architect & Q-Developer, for the outside assessment, which we checked finding by finding in the code. He publishes his own security material in his repository. It is independent of RagLeap, we have not reviewed its contents, and the link is not an endorsement. Thanks also to everyone who tested and reported. More: our release page and the roadmap.

Quick answers

What did the outside assessment of RagLeap Core find?

An outside researcher, Aleksei Musienko of AMQIC, sent a static assessment, and we checked each finding in the code. v0.13.4 fixes four: an approval could run twice, file approval could be skipped by a mismatched label in full mode, a group chat could approve as the owner, and update backups and Redis credentials could end up in an image build and a log.

Is RagLeap Core security certified?

No. The assessment was a static code review by one outside researcher. It is not a certification, and the outside review of file writing (#800) has not happened.

Where does RagLeap accept approvals in chat?

Only from a private, one-to-one conversation with the owner: a private Telegram chat or a Discord direct message. Approvals typed in a group or a server channel are ignored.

Do I need to change a setting to upgrade to v0.13.4?

No new setting. If you run your own database, apply the additive block in db/schema.sql, then rebuild and restart. File writing, deleting and sub-agents stay off.

Back to the blog