Who Is Responsible for Security Updates in Modern Software?
Daniel Nashed – 18 November 2026 20:29:48
A friend asked me today when his Linux distribution would provide the security fixes for the newly disclosed NGINX vulnerabilities.
It sounds like a simple question. But it illustrates a much larger problem with modern software: Who actually provides the security fixes for the software we are running?
Upstream Projects and Linux Distributions
When a vulnerability is discovered, the original software project usually provides a fix.
But most Linux installations don't use software directly from the original project. Instead, they use packages maintained by their Linux distribution.
Distributions such as Debian, Ubuntu, and Red Hat often maintain their own package versions. Rather than upgrading to the latest upstream release, they may backport security fixes into an older version.
This is generally a good approach for stability, but it makes security status harder to recognize.
An older version number does not necessarily mean a package is vulnerable. Conversely, the latest package available in a distribution does not necessarily contain a newly released security fix.
Administrators need to check the distribution's security advisories and package changelogs rather than relying only on version numbers.
Products Built on Other Products
The situation becomes more complicated when software projects depend on other complete products.
The new NGINX2Root disclosure provides a good example:
NGINX → OpenResty → Apache APISIX
NGINX has already released patched versions, but OpenResty must integrate the fixes into its own NGINX-based distribution. Apache APISIX then depends on the corresponding OpenResty updates.
Each additional layer introduces another release cycle, testing process, and potential delay.
The same applies to commercial products that embed open-source components.
Why Containers Can Be the Better Deployment Model
This is one reason I increasingly prefer container-based deployments.
With traditional Linux packages, the application depends on the operating system distribution and its package maintenance schedule.
With containers, the application vendor can provide a complete, tested runtime environment, including the required software components and dependencies.
This offers several advantages:
- Independent updates: Applications can be updated without waiting for the host distribution to upgrade its packages.
- Consistent environments: The same tested software stack can run on different Linux distributions.
- Simpler deployment: A new image can replace the previous one without modifying the host's application packages.
- Controlled rollbacks: Previous image versions can be retained and redeployed if necessary.
For example, we have already rebuilt our NGINX container image with the patched NGINX 1.31.9 release, without waiting for a Linux distribution to provide an updated package -- which is usually a patch not a roll up to the latest version.
None of our supplied configurations enables HTTP/2 out of the box, but we updated anyway because not all NGINX2Root vulnerabilities depend on HTTP/2.
Of course, containers do not automatically solve security problems. The image maintainer must still track vulnerabilities, update dependencies, and rebuild images promptly.
And containers share the host's Linux kernel, which remains the responsibility of the host administrator.
The critical difference is how quickly fixes become available, how transparently they are documented, and how reliably administrators can deploy them.
Conclusion
Security maintenance is no longer just about installing the latest software version.
We need to understand where our software comes from, which components it includes, who maintains them, and how security fixes reach our systems.
Containers can simplify this process considerably by separating application updates from operating system updates — provided that the container images themselves are actively maintained.
The NGINX2Root disclosure is a timely reminder that security fixes must travel through the entire software supply chain before they actually protect the systems we operate.
In my case I shutdown my Domino Download server which is based on OpenResty as a precaution.
As we just learned it does not have the patches. They released a new version in October on a quite new NGINX verison, but that version does not contain the security patches yet.
- Comments [0]