Skip to content

Security Policy

github-actions[bot] edited this page Oct 27, 2026 · 3 revisions

Security policy

Reporting a vulnerability

Please do not open a public issue for security problems (a script that escapes the VM, corrupts memory, crashes the firmware, breaks the VFS confinement, ...). Report it privately through GitHub security advisories with a script or steps that reproduce it. You will get an answer within a few days, and a fix is released as soon as it is ready, with credit if you want it.

Supported versions

Fixes go into the latest release (see CHANGELOG.md).

Security model

What MicroCS does and does not protect against (memory safety, heap and time limits, module whitelisting, VFS confinement) is described in docs/SECURITY.md.

Clone this wiki locally