Enterprise applications rarely break because of custom business logic; instead, the issue is often related to changes in underlying open source dependencies. When a high-severity vulnerability is found in a third-party library, organizations face a difficult trade-off—rush a major version upgrade and risk production outages, or remain vulnerable while waiting for validation cycles. Resolving this tension requires looking upstream to the original open source community where the software is authored and maintained. A security fix has to reach the dependency version an enterprise runs.

When the flaw also affects the originating open source project, remediation includes working with its maintainers to fix the shared codebase. Imagine a verified vulnerability in a dependency your production application keeps at a pinned version (a specific software version it deliberately continues to use). Upgrading to the latest major release isn't always viable on short notice—it can disrupt mission-critical APIs, trigger costly regression cycles, or violate regulatory certifications. An upgrade also requires extensive compatibility testing.

Lightwell is a joint IBM and Red Hat initiative that provides security remediations and mitigations for eligible third-party open source dependencies through a subscription model. It's designed to help organizations address vulnerable dependencies when an ordinary version upgrade poses compatibility, certification, or production risk. In that application, suppose a newer upstream release already corrected the affected behavior. The pinned release remains vulnerable. A correction in the shared project doesn't automatically reach an application built around an older version.

If the newer release meets the application's compatibility and deployment requirements, upgrading may be the right choice. When an upgrade can't immediately fit those requirements, a backport (a correction adapted for an older software release) offers another path to evaluate. It targets the affected behavior in the older code, giving the application developer a narrower change to test than a release with unrelated changes. The application still needs testing, of course—a smaller change can affect behavior, too. Artifact identity helps connect that decision to the build.