# Chainguard: Build and runtime failures related to the OpenSSL 4 transition

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-10-06 15:08 UTC · Resolved: 2026-10-16 20:32 UTC · Duration: 10 d
- Updates: 8 · Affected components: Image builds & releases
- Vendor status page: n/a
- [Company: Chainguard](https://rewindex.com/company/chainguard.md)

## Timeline of updates

- **degraded** 2026-10-06 15:08 UTC: Some customers are seeing build or runtime failures related to the ongoing Chainguard OS transition to OpenSSL 4, mostly when adding packages to an image with apk add or copying binaries between images. Fixes are available or rolling out for the affected images, and building from a current image with current packages resolves most cases. If you are affected, please contact support with your image digest and the error output.
- **degraded** 2026-10-06 16:27 UTC: Some customers are seeing build or runtime failures related to the ongoing Chainguard OS transition to OpenSSL 4, mostly when adding packages to an image with apk add or copying binaries between images. We continue to work through other reports related to the OpenSSL 4 transition. If you are affected, please contact support with your image digest and the error output, including errors related to OpenSSL or cipher suites.
- **degraded** 2026-10-06 17:24 UTC: Some customers are seeing build or runtime failures related to the ongoing Chainguard OS transition to OpenSSL 4, mostly when adding packages to an image with apk add or copying binaries between images. We continue to work through other reports related to the OpenSSL 4 transition. If you are affected, please contact support with your image digest and the error output, including errors related to OpenSSL or cipher suites.
- **degraded** 2026-10-06 22:21 UTC: Additional information on troubleshooting and resolving issues with affected images is forthcoming. We will provide a link to the updated documentation when it goes live. Some customers are seeing build or runtime failures related to the ongoing Chainguard OS transition to OpenSSL 4, mostly when adding packages to an image with apk add or copying binaries between images. We continue to work through other reports related to the OpenSSL 4 transition. If you are affected, please contact support with your image digest and the error output, including errors related to OpenSSL or cipher suites.
- **degraded** 2026-10-08 20:06 UTC: Guidance on troubleshooting and resolving issues with affected images is available here (paid customer login required): https://support.chainguard.dev/hc/en-us/articles/56956385560219-ACTION-RECOMMENDED-OpenSSL-4-transition-may-cause-build-and-runtime-failures. Please check your email, Slack messages, or Activity Console, according to your communications opt-ins with us, as we have also sent it there according to your preferences. We are monitoring the incident, and are still moving forward with the OpenSSL 4 ABI migration. If you experience any issues you believe are related to the migration from OpenSSL 3.6 to 4.0 at this time, please contact Support.
- **degraded** 2026-10-09 21:35 UTC: We continue monitoring and resolving issues related to the OpenSSL 4 transition. More fixes for specific OpenSSL 3/4 compatibility issues are in testing or already deployed. If you’re seeing build or runtime errors, follow the steps under “What you can do now” in our \[troubleshooting guide\](https://support.chainguard.dev/hc/en-us/articles/56956385560219-ACTION-RECOMMENDED-OpenSSL-3-to-4-transition-may-cause-build-and-runtime-failures) (login required). If you still have issues after following that guidance, contact Support with your image digest and the full error.
- **degraded** 2026-10-11 22:25 UTC: Through this weekend we have solved many issues related to the OpenSSL 4 transition. Most classes of issues we have observed have effective fixes released. If you have outstanding tickets, please review them for additional information or requests for your specific issue. If you’re seeing build or runtime errors for the first time on this topic, follow the steps under “What you can do now” in our \[troubleshooting guide\](https://support.chainguard.dev/hc/en-us/articles/56956385560219-ACTION-RECOMMENDED-OpenSSL-3-to-4-transition-may-cause-build-and-runtime-failures) (login required). If you still have issues after following that guidance, contact Support with your image digest and the full error.
- **resolved** 2026-10-16 20:32 UTC: This issue has been resolved. The OpenSSL 4 transition is complete, all Chainguard images and packages are now on OpenSSL 4, and our services are operating normally. Customers whose builds mix OpenSSL 3 and OpenSSL 4, or who run prebuilt software that still needs the OpenSSL 3 libraries, have been contacted directly with migration steps and a hardened OpenSSL 3.5 option.  For full details, see our knowledge base article: \[KB: OpenSSL 4 transition complete and a hardened OpenSSL 3.5 option\](https://support.chainguard.dev/hc/en-us/articles/57324590326299-UPDATE-OpenSSL-4-transition-complete-and-we-now-publish-a-hardened-OpenSSL-3-5-option-with-security-updates-that-follow-OpenSSL-s-upstream-support-timeline)


---
Canonical: https://rewindex.com/company/chainguard/incidents/1083228 · Markdown: https://rewindex.com/company/chainguard/incidents/1083228.md · JSON: https://rewindex.com/api/v1/companies/chainguard/incidents/1083228 · Generated 2026-10-19T23:35:21.095Z