Resolved after 3 days, affecting Docker Jobs, on November 7, 2025.
We have identified and applied a workaround for the RAM DIsk issue, which means customers can resume builds using `/mnt/ramdisk`. We appreciate your patience and understanding whilst we worked on resolving this whilst ensuring the security of our platform for all customers.
Affected components
Update timeline
- monitoring Nov 07, 2025, 10:40 AM UTC
At present customers running Docker containers cannot use /mnt/ramdisk. Customers will need to modify their configuration to use the filesystem instead. This has occurred in order to update the Docker Infrastructure that supports our `working_directory: /mnt/ramdisk` feature. This is a necessary step in order to address CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881. This bug affects any Docker jobs utilizing `working_directory: /mnt/ramdisk`. Jobs will fail on checkout and workspace attachments. The immediate workaround will be to remove any usage of `working_directory: /mnt/ramdisk` from your job which will require an update of `.circleci/config.yml` Once this maintenance is complete, customers will be unable to utilize `working_directory: /mnt/ramdisk`until further notice.
- resolved Nov 10, 2025, 11:24 AM UTC
We have identified and applied a workaround for the RAM DIsk issue, which means customers can resume builds using `/mnt/ramdisk`. We appreciate your patience and understanding whilst we worked on resolving this whilst ensuring the security of our platform for all customers.
Your product runs on more than Circle CI
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services