Four build-level mitigations do the work that separates memory-safety-bug-as-DoS from memory-safety-bug-as-RCE. Position Independent Executable builds plus ASLR randomize the virtual address space, forcing any gadget chain to acquire a base-address leak before it is usable. Stack canaries insert a per-process secret between local variables and the saved return address, so a linear stack overflow that reaches saved RIP must first read the canary out through some other primitive. FORTIFY_SOURCE rewrites length-aware libc calls at compile time to abort on size violations the compiler can prove, turning a subset of overflows into controlled aborts and blocking %n format-string writes into writable GOT entries by rewriting printf to __printf_chk. Full RELRO maps the GOT read-only after dynamic linking, removing the single most common write target an attacker reaches for once they have an arbitrary write primitive. A binary with all four shipping default-on is not unexploitable; it is a binary where exploitation requires a chained second primitive (information leak, write-what-where, arbitrary read) that the one memory bug may or may not provide. A binary with all four off presents the saved RIP, the GOT, and a static gadget table as a single step.
The compilation toolchain decides which of these bytes end up in the shipped ELF. The source code does not; the CVE record does not; the researcher's PoC does not. A vendor that ships a 2026 firmware with a binary carrying no PIE, no canary, no FORTIFY, and partial RELRO has made a build-system choice decades after the toolchain made the safer choice available. The choice is inherited by every binary the same build pipeline emits, so the next CGI handler, the next long-running daemon, and the next IPC helper in the same image carry the same amplifier. When a memory bug is disclosed and patched in one function, the patched release ships the source fix and leaves the amplifier in place. The next source-level bug in the same binary reaches the same amplifier and carries the same exploitability class. The exhibit set shows the shape at three scales: a NAS vendor's CGI with eight sscanf overflows and a format string on a binary with zero mitigations (CVE-2026-6643, ASUSTOR vpnupload.cgi); a drone autopilot with a sixty-byte filepath overflow on a NuttX build whose stack canary coverage is absent on the affected compile unit (CVE-2026-32743, PX4); a firewall VPN daemon whose public exploit lists absolute virtual addresses for its ROP gadgets because the binary is not position-independent (CVE-2025-9242, WatchGuard iked).
The observable signature in a CVE record is the gap between the researcher's working exploit and the maintainer's patch. The exploit's gadget table contains absolute virtual addresses; the overflow reaches saved RIP without a canary-recovery step; %n writes against the GOT succeed without being rewritten to __printf_chk. The patch fixes the bounds check or the format string. The build system is not touched. On the next CVE in the same binary, the attacker reuses the same absolute addresses because the binary is not position-independent, and the exploit that worked on version N works on version N+1 with a single offset change. The amplifier is not a bug in a function. It is the default state of a toolchain configuration nobody reread when the function was patched.