Repository navigation
Sage
Mutant v2.6.0 "Sage"
Released 2026-10-12. Every answer checked, or refused out loud.
Sage is the X-Men mutant with a computer's mind and total recall, and she
follows 2.4.0 "Legion" in the line of codenames. This release is named for the
habit it asks of Mutant: if a builtin cannot be sure of an answer, it says so.
It should never give an answer that looks right and is wrong.
2.6.0 grew out of a line-by-line review of the whole toolchain. Since 2.5.0 the
standard library has grown from 497 to 694 builtins, and the changelog
records 37 additions, 30 changes, 140 fixes and 25 security fixes. Thirteen
security advisories are published with it.
Upgrade if you run 2.5.0 or earlier. There is no 2.5.x patch release.
Security fixes land on the latest minor only, so 2.6.0 is the fixed version
for every advisory below.
Before you upgrade: five breaking changes
Most programs compile unchanged. Of the 123 example programs that existed when
the block-scope rule landed, two needed edits for it. Check yours for these five
things:
- A block is a scope, and a
letmust declare something new. A name
declared inside{ ... }no longer exists after the closing brace. Inside
one scope,let x = 1; let x = 2;is refused; writex = 2. The
let value, err = ...idiom still works, because the value name is new each
time. One change still compiles but gives a different answer. Alet
inside a block that reuses an outer name now declares a new variable instead
of changing the outer one.mutant lintreports the inner variable as
unused. - Assigning to an undeclared name is refused.
y = 1without an earlier
let ynow fails with "cannot assign to y: y is not declared". - Values of different types are not equal.
null == "","0" == 0and
"true" == trueare now false, in both engines. An integer and a float still
compare by value. Arrays, hashes and structs compare element by element. - An import names the same file on every system (affects Windows). A
backslash is a separator everywhere. Mutant refuses a path that Windows and
other systems would read differently, such as one with a trailing dot or
space, or a leading/with no drive letter. - A bare
--passwordis refused, as 2.5.0 announced. Use the prompt (the
default),--password-file,--password-stdin, or
--password-insecure <value>if you accept that other local users can
read it from the process list.
VS Code extension users: update to extension 0.3.0, released with 2.6.0.
0.2.0 bundles the 2.5.0 language server, so every builtin new in 2.6.0 shows as
an undefined identifier, and its release task sends password as --password,
which 2.6.0 refuses. 0.3.0 bundles the 2.6.0 server and passes
--password-insecure, and it adds passwordFile.
Programs compiled by 2.3.x now call the builtins they were compiled for.
Programs compiled by 2.2.x or earlier should be recompiled from source.
Highlights
Filesystems you can trust in court
- Partitions open where they lie.
ntfs_open,ext_openand the other
openers take a partition fromtable_list_partitions, so you can work on a
whole disk image without extracting the partition first. - Files stream instead of loading whole. Eighteen builtins read large files
in pieces. - What a filesystem remembers about files that are gone:
- deleted-entry scans and
*_recover_file; - nine journal readers, for the NTFS USN journal and
$LogFile, ext's JBD2
and the XFS log. Each says whether its scan crossed the point where the
journal wraps around; - file slack and unwritten space;
- NTFS alternate data streams, extended attributes, security descriptors,
reparse points and HFS resource forks; - VHD and VHDX extents, sparse areas and differencing chains.
- deleted-entry scans and
- Integrity that is checked, not just reported.
verifiedis two facts:
whether a check ran and whether it passed. It is never one boolean. Each of
the six filesystem libraries has a*_capabilitiesbuiltin, which says what
the format can record (supported, unsupported or unanswered). Each also has a
*_reportbuiltin, which walks a whole volume into one row shape that the
ECS, OCSF and Timesketch emitters accept.
A forensic ledger, cases and disclosure
ledger_*: thirty-nine builtins for an append-only, tamper-evident case
ledger. They cover proofs, custody, anchoring to a witness, redaction with a
recorded reason, and reading the ledger back.- Classified records and case keys.
case_key_*andrecord_*seal
evidence in.mreccontainers. Plaintext read from a classified record cannot
leave the process by accident, and the editor warns you first. - Disclosure.
view_*,disclose_*, roles and redaction versions let you
share selected segments with a recipient under a passphrase. A withdrawal is
recorded, along with who made it and on whose authority. - Custody and review. An exhibit has a custody chain from intake. A case
keeps its state in its ledger and can be reviewed, held, retained and erased
on the record.
Graphs and data
mutant graph exportandmutant graph query, plusdb_compactand a
memory budget for disk-backed graph stores.- A
db_*store can be read back, and relation labels are stored rather
than dropped.
The language and its tools
exec_argv(argv)runs a program with exactly the arguments given, with no
shell in between.mutant fmtkeeps the brackets you wrote and adds none.- The editor knows what builtins accept. It warns on an argument that is not
one of a builtin's choices, flags case-builtin mistakes, and warns when a
macro body does something it may not. It resolves names across modules the way
the compiler does. - Runtime errors say what you wrote. A refused comparison reads
unknown operator: INTEGER < NULL, not an opcode number.
For contributors
- A release gate you can run:
scripts/release_gate.ps1and.shrun the
same checks the maintainer runs before tagging and print one table. - The documentation is checked against the tree. Tests check every
mutant
code block, cited path, link, builtin name and stated version against the
code. - 127 runnable example programs. The 84 that run without outside input are
compared with their recorded output.
Security
There are thirteen advisories in total. Two are S1, and seven concern code that
a released version contained. The full register is
docs/advisories.
| Advisory | Severity | Affected | What it was |
|---|---|---|---|
| MVF-2026-0001 | S1 | 2.2.0 – 2.5.0 | Compiling a program ran whatever builtins its macros called |
| MVF-2026-0007 | S1 | 2.3.0 – 2.5.0 | A SQL query the documentation called read-only could modify evidence |
| MVF-2026-0005 | S2 | all through 2.5.0 | Two strings sharing one 64-bit digest were one hash entry |
| MVF-2026-0012 | S2 | 2.3.0 – 2.5.0 | A header count sized an allocation before its bytes were there |
| MVF-2026-0013 | S2 | 2.3.0 – 2.5.0 | A binary plist sharing its containers expanded exponentially |
| MVF-2026-0009 | S3 | 2.1.0 – 2.5.0 | An inherited environment variable chose the signing key and trust anchor |
| MVF-2026-0010 | S3 | extension 0.1.0 – 0.2.0 | The extension's release task passed the password in the argument list (fixed in extension 0.3.0) |
The other six advisories (0002, 0003, 0004, 0006, 0008 and 0011) concern code
that first ships in 2.6.0. Each is published anyway, so you never have to infer
anything from a gap in the numbering.
Also in this release:
- the toolchain moves to Go 1.26.9,
golang.org/x/cryptoto v0.57.0 and
golang.org/x/netto v0.60.0. Together they fix 29 Go standard library
vulnerabilities that Mutant's code reaches: 18 present in go1.26.2 and 11 more
in go1.26.6, innet/http,crypto/tls,mime/multipartandos. A release
binary compiles the standard library in, so this matters to everyone who runs
one; - Mutant's own code reads no configuration from environment variables, and a
guard in the test suite enforces this.HOME,USERPROFILE, the proxy
variables andHOST_PROCno longer change what Mutant does. Two dependencies
still consultZONEINFOandTZ(see Known issues).
Known issues
Forty-nine wrong answers found during the review are not fixed in this release.
Each is tracked for the next one. The full list, with workarounds, is under
Known issues in CHANGELOG.md. The ones you are most likely
to hit:
+,-and*wrap silently on 64-bit overflow.mutant releasehas no darwin/arm64 or windows/arm64 runtime.- A password file written by Windows PowerShell (with a byte-order mark, or in
UTF-16) silently changes the password. Write it as UTF-8 without a BOM. hive_get_valueandreg_get_valuecannot find the unnamed value by the name
(default)that the listing builtins give it.fs_existsreturns true when a path cannot be checked for some reason other
than "does not exist".- A Rego policy's named time zones, and SQLite's
localtime, depend on the
host. Use UTC where that matters.
Workshop
examples/workshop/ holds QUILLDROP, a two-hour guided investigation built
for the DFRWS APAC 2026 workshop. It has ten beats and four deep dives: registry
Run keys, cookies against history, browser redirect chains, and $SI/$FN
timestomping. The rehearsal script refuses any binary other than 2.6.0. A script
whose input is missing names that input and stops.
Install
Download the binary for your platform from this release, or build from source:
git clone https://github.com/aoiflux/mutant
cd mutant
./scripts/build.sh --host-only # Windows: ./scripts/build.ps1 -HostOnlyA plain go install builds a working compiler and runtime, but mutant release
needs the runtime assets that the build scripts embed.
Release targets: darwin/amd64; linux/amd64, 386, arm64 and arm; windows/amd64
and 386.
Full changelog: CHANGELOG.md · Compare:
v2.5.0...v2.6.0