The default file-based session save handler writes updated session data into existing files without clearing them first. If a write operation is interrupted, the resulting file may contain a mix of new and old session data. An attacker capable of influencing session data, such as through session upload progress during an unauthenticated file upload, can interrupt the write process to inject objects. When the application later unserializes this corrupted data, it can lead to remote code execution if a suitable gadget chain exists. This process can also result in session data corruption.