CVE-2026-1386: 
NixOS vulnerability analysis and mitigation

CVE-2026-1386 is a UNIX symbolic link (symlink) following vulnerability in the jailer component of Amazon Firecracker, an open-source microVM virtualization technology. It affects Firecracker versions v1.13.1 and earlier, as well as version 1.14.0, running on Linux. The flaw may allow a local host user with write access to pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, provided the jailer is executed with root privileges. It was published on January 23, 2026, and carries a CVSS v4.0 base score of 6.0 (Medium) (AWS Security Bulletin, GitHub Advisory).

The vulnerability is classified as CWE-61 (UNIX Symbolic Link Following), where the jailer component does not sufficiently validate whether a file at the destination path is a symbolic link before performing a binary copy during initialization (GitHub Advisory). During jailer startup, the initialization process copies binaries into the jailer directory; if an attacker has pre-placed a symlink in that directory pointing to an arbitrary host file, the copy operation — running as root — will overwrite the symlink target (AWS Security Bulletin). Exploitation requires two preconditions: the attacker must have local write access to the pre-created jailer directories, and the jailer must be executed with root privileges. The fix in v1.13.2 and v1.14.1 updates the binary copy process to disallow symlinks and hardlinks at the destination path and changes ownership of the copied binary to the specified uid/gid (Firecracker v1.14.1, Firecracker v1.13.2).

Successful exploitation allows a local privileged user to overwrite arbitrary files on the host filesystem, including critical system files, configuration files, or binaries, potentially leading to full host compromise. The primary impacts are to integrity and availability of the host system — confidentiality is not directly affected as the attack overwrites rather than reads files (GitHub Advisory). Overwriting sensitive host files (e.g., /etc/passwd, init scripts, or privileged binaries) could enable privilege escalation, persistence, or denial of service on the host running Firecracker microVMs. AWS has confirmed that its own services using Firecracker are not impacted due to additional access restrictions on the host and jailer folder (AWS Security Bulletin).

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time (Feedly). The EPSS score is approximately 0.007%, reflecting a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation is constrained by the requirement for local access with write permissions to jailer directories and root-privileged jailer execution, significantly limiting the attacker pool.

1. Identify a vulnerable target: Confirm the host is running Firecracker v1.13.1 or earlier, or v1.14.0, with the jailer executed as root.
2. Gain write access to jailer directories: Obtain local user access with write permissions to the pre-created jailer directories (e.g., through a compromised local account or misconfigured permissions).
3. Place a malicious symlink: Before jailer startup, create a symbolic link inside the jailer directory at the expected destination path of the binary to be copied, pointing to an arbitrary target file on the host (e.g., ln -s /etc/cron.d/malicious /path/to/jailer/dir/firecracker).
4. Trigger jailer initialization: Wait for or trigger a jailer startup event, which initiates the binary copy process running as root.
5. Achieve arbitrary file overwrite: The jailer's copy operation follows the symlink and overwrites the target host file with attacker-controlled content, potentially enabling privilege escalation, persistence, or denial of service (GitHub Advisory, AWS Security Bulletin).

• File System: Unexpected symbolic links present in jailer pre-created directories (e.g., directories under the jailer chroot path) pointing to sensitive host files outside the jailer scope.
• File System: Unexpected modifications to critical host files (e.g., /etc/passwd, /etc/shadow, cron directories, or system binaries) with timestamps correlating to jailer startup events.
• Logs: System logs (e.g., /var/log/syslog, /var/log/auth.log) showing file write operations by the root-privileged jailer process to unexpected paths outside the jailer directory.
• Process: Jailer process (jailer binary) performing file copy operations that result in writes to paths outside the expected chroot environment.

Users should upgrade to Firecracker v1.13.2 or v1.14.1 (or later), which update the binary copy process to disallow symlinks and hardlinks at the destination path (Firecracker v1.14.1, Firecracker v1.13.2). For users unable to upgrade immediately, AWS recommends restricting access to the jailer directory using UNIX permissions — specifically using chown and chmod 700 to limit access to only trusted users (AWS Security Bulletin). Additionally, operators should audit which local users have write access to jailer directories and minimize the use of root privileges for jailer execution where possible.

AWS published a formal security bulletin (2026-003-AWS) on January 23, 2026, noting that its own services using Firecracker are not impacted due to existing access controls, and credited an independent security researcher for responsible disclosure (AWS Security Bulletin). The vulnerability received moderate attention in the security community, with mentions on Infosec Exchange and a technical write-up published at infinitsec.net shortly after disclosure. Community sentiment reflects the view that the vulnerability's impact is limited by its strict preconditions, and the availability of patches reduces urgency for most operators.