Security incident · RUSTSEC-2026-0412
Arbitrary code execution when rerunning tests from a portable recording
Published Oct 26, 2026 · RustSec Rust
Last checked Oct 27, 2026. A connected source was read within the last 7 days.
Open the advisory
Exploitation likelihood is not on this record for RUSTSEC-2026-0412. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.
Gaps on this record
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
Same product and reporting
- RUSTSEC-2026-0413 · Unknown
- RUSTSEC-2026-0408 · Unknown
- RUSTSEC-2026-0409 · Unknown
- RUSTSEC-2026-0385 · Unknown
- RUSTSEC-2026-0387 · Unknown
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Not established
- Affected products
- RustSec Rust
## Summary Nextest versions between 0.9.125 and 0.9.149 (inclusive) allow the (or ) command with a malicious [portable recording](https://nexte.st/docs/features/record-replay-rerun/portable-recordings/) to run arbitrary code during the build. The result is arbitrary code execution with the privileges of the user running . This vulnerability requires that the experimental [run recording](https://nexte.st/docs/features/record-replay-rerun/) functionality is enabled. An attacker can plausibly trick a victim into enabling this feature. ## Details Nextest's portable recordings contain [build scope
No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.
How to fix RUSTSEC-2026-0412
No stored fix
No vendor fix text is stored. Use the linked advisory before you change production.
Version check
No version range is stored, so an installed version cannot be checked on this page.
Advisory
Open the rustsec record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for RUSTSEC-2026-0412. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 26, 2026 · RustSec Advisory DB
Detected
## Summary Nextest versions between 0.9.125 and 0.9.149 (inclusive) allow the (or ) command with a malicious [portable recording](https://nexte.st/docs/features/record-replay-rerun/portable-recordings/) to run arbitrary code during the build. The result is arbitrary code execution with the privileges of the user running . This vulnerability requires that the experimental [run recording](https://ne
Sources
- RustSec Advisory DBVendor advisoryRUSTSEC-2026-0412
## Summary Nextest versions between 0.9.125 and 0.9.149 (inclusive) allow the (or ) command with a malicious [portable recording](https://nexte.st/docs/features/record-replay-rerun/portable-recordings/) to run arbitrary code during the build. The result is arbitrary code executio
crates.io
Freshness
Last verified in this catalog Unknown date. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- RustSec Advisory DBOct 27, 2026