Preliminary research

Write Once, Shell Everywhere: Turning Arbitrary File Writes into RCE

André Baptista, Rafael Castilho and Bruno Mendes · Ethiack

AI-collected research leads through 3 November 2026, including a November–October–September missed-article review and a targeted multilingual search alongside earlier community-source sweeps. Unranked, incomplete, not community-vetted, and subject to change.

A graded catalogue of arbitrary-file-write to RCE sinks, plus new ones. Path resolution stops at the first failing component, so the errno of a failed write - read through status code, body length or latency - fingerprints OS, container, distro and runtime version. Guess-free targets follow: PID 1's still-open entrypoint script at /proc/1/fd/255 or /proc/1/fd/10, a worker pool's fixed worker.js, and Rails db/schema_cache.yml, unsafe_load'd into a RubyGems hash-key gadget chain.

Record

Researcher

André Baptista, Rafael Castilho and Bruno Mendes

Published by

Ethiack

In the archive

• Collected in the 2026 preliminary research sweep

Tags

• rce
• side-channel
• gadget-chain
• deserialization
• docker
• nodejs
• ruby
• info-leak
• owasp-a05-2021
• owasp-a08-2021

This page is the archive's own catalogue record. The research is the work of André Baptista, Rafael Castilho and Bruno Mendes, first published at the original source. Preserved copies are kept so the citation survives its host.