On this page (6 sections)
On November 17, 2026, Debian published DSA-6618-2, a regression update for the openexr package. It follows the earlier security update DSA-6618-1, whose packages failed to build on the i386 architecture.
If you run Debian 13 (trixie) servers, especially ones with both amd64 and i386 versions of the OpenEXR library installed, this update is worth applying. It is a packaging fix, not a new vulnerability disclosure.
What happened
According to the Debian advisory, the OpenEXR security update announced in DSA-6618-1 failed to build on i386 because of test-suite failures. As a result, i386 packages for that update were missing.
Debian points out a practical consequence: the missing i386 packages could also prevent upgrades on multiarch systems that have both amd64 and i386 versions of the library installed.
The follow-up update, DSA-6618-2, is Debian's fix for that gap. The advisory states plainly that no additional vulnerabilities are addressed by it.
What the update changes
The advisory describes two changes to how the package is built:
- It enables SSE2 floating-point code generation for i386.
- It makes test-suite failures non-fatal during package builds on big-endian architectures.
Both are build-level adjustments. The advisory does not describe any change to how OpenEXR handles image files, so this update is best read as getting the earlier fix delivered to every architecture.
Who is affected
The advisory targets the stable distribution, trixie, with fixed version 3.2.12-1~deb13u2. Systems most likely to notice a problem are:
- Multiarch hosts with both amd64 and i386 OpenEXR libraries installed, where upgrades could be blocked.
- i386 systems that did not get the DSA-6618-1 packages because the build failed.
The advisory does not say which applications use the library, so check your own dependencies. A server that has no OpenEXR packages installed has nothing to update here.
How to check your exposure
This read-only command lists installed openexr-related packages with their versions and architectures on Debian. Look for versions older than 3.2.12-1~deb13u2 on trixie.
dpkg -l | grep -i openexrThis read-only command shows which foreign architectures dpkg is configured to use. If i386 is listed on an amd64 host, your system is multiarch, which is the case the advisory describes.
dpkg --print-foreign-architecturesWhat to do now
- Confirm you are on Debian 13 (trixie) and list your openexr packages with dpkg.
- Check whether i386 is enabled as a foreign architecture on the host.
- Refresh package lists and upgrade the installed OpenEXR packages to 3.2.12-1~deb13u2 or later.
- If an earlier upgrade stalled or held back packages on a multiarch system, retry after refreshing package lists.
- Verify the installed version afterwards on every host.
- Review the original DSA-6618-1 and the Debian security tracker so you know what the underlying security fix covers.
This command refreshes package lists on Debian. Run it as root or with sudo; it changes no installed packages.
sudo apt updateThis command upgrades packages that are already installed, including openexr, to the versions available in your configured trixie repositories. Run it as root or with sudo and review the proposed package list before confirming.
sudo apt upgradeThis read-only command confirms the result. The version column should read 3.2.12-1~deb13u2 or newer for each OpenEXR package on trixie.
dpkg -l | grep -i openexrMonitoring and follow-up
Regression updates like this one are a reminder to treat patching as a process with verification, not a single command. After upgrading, confirm the version on every host, including ones with unusual architecture setups, and make sure automatic updates are not silently failing.
If you manage several Debian servers, keep an eye on the Debian security announcements and the openexr security tracker page for further changes. For the web-facing side of your servers, certificate and header changes can be tracked with Webforta Monitor, and the security guides cover broader hardening. This is a Debian package matter, so an outside-in website scan will not tell you whether a system library is up to date.
For other security news that may affect your servers and sites, see the Webforta blog.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
