RagLeap
Blog

Outside security assessment of RagLeap Core: Aleksei Musienko (AMQIC) and what we fixed

In November 2026 an outside researcher, Aleksei Musienko of AMQIC, assessed RagLeap Core (ragleap-core) and sent us a written report. This page says who he is, what he did, what we did with it, and what is still not done. It is a plain account and not a certification. The facts come from our public release notes for v0.13.4 and v0.13.5, checked on 2026-11-18.

Who is Aleksei Musienko?

Our release notes credit him as Chief Scientist & Founder of AMQIC (MSEC), QIAIMP Scientist, Q-Architect & Q-Developer, with the assessment powered by CERNOTIS. These are his own descriptions of his role and employer, and we have not verified them independently. He publishes security material for developers in a public repository that GitHub describes as AMQIC's default cybersecurity for applications, free for every developer. It is independent of RagLeap. We have not reviewed its contents, and the link is not an endorsement.

What did he do for RagLeap?

He sent a written assessment of ragleap-core. It was a static review, which means the code was read for weaknesses. We did not take the findings on trust: each finding we acted on was checked by us in the code first. He agreed to be named, and he asked us to share his work with our readers, which this page does.

Which findings did we confirm and fix?

  • v0.13.4 (2026-11-17): an approval runs only once (#1444); file actions always need approval and a mismatched label and channel are refused (#1445); chat approvals are accepted only from a private chat (#1447); update backups stay out of the image build and Redis credentials stay out of the log (#1446). Read the post.
  • v0.13.5 (2026-11-17): old approvals expire after 7 days by default (#1455); Discord requests with an old timestamp are refused (#1456); connector credentials fail closed without an encryption key, and the Mongo connector no longer splices the user identifier into JSON text (#1462). Read the post.

What does this mean for the status of RagLeap Core?

It means an outside person read the approval and connector code closely, and the problems we confirmed were fixed in public releases with release notes. It does not mean RagLeap Core is certified, or secure by itself. The assessment was static and by one researcher, and the outside review of file writing (#800) has not happened. We do not claim that every item of his report is closed.

What other security work is public?

How do I report a vulnerability?

Please do not open a public issue. Use a private report through GitHub Security Advisories, or follow SECURITY.md. Our security page lists known issues.

What is not done?

  • The outside review of file writing (#800) has not happened. Keep file writing off in production.
  • Nothing here is a certification or a compliance claim.
  • The "not independently audited" labels on our libraries are not changed by this assessment.

Quick answers

Who assessed the security of RagLeap Core from outside?

Aleksei Musienko of AMQIC, credited in our release notes as Chief Scientist & Founder of AMQIC (MSEC), QIAIMP Scientist, Q-Architect & Q-Developer, sent a written static assessment of ragleap-core in November 2026. We have not independently verified his titles.

Was RagLeap Core tested or certified?

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

What did RagLeap fix after the assessment?

Seven fixes in two releases: v0.13.4 (approvals run once, file actions always need approval, approvals only from a private chat, backups and Redis credentials out of images and logs) and v0.13.5 (old approvals expire, Discord replay protection, connector credentials fail closed).

How do I report a security problem in RagLeap?

Do not open a public issue. Use a private GitHub Security Advisory or follow SECURITY.md in the ragleap-core repository.

Back to the blog