Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

WebKitGTK and WPE WebKit: Patch the 2.54.3 Security Update

WebKitGTK and WPE WebKit security update covers 26 CVEs. See which upstream versions are affected and how to verify patched distribution packages.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
19 November 2026
Reading time
3 min read
Two abstract browser rendering layers protected by a repaired shield on a dark navy background.

The WebKitGTK and WPE WebKit security update addresses 26 CVEs in the projects’ 18 November 2026 advisory. Operators should move to the latest stable release, with 2.54.3 covering every listed issue. Check distribution packages as well as upstream versions before closing the patch ticket.

The advisory separates crashes and memory corruption from flaws that may permit arbitrary code execution. Its impact descriptions concern processing maliciously crafted web content. They do not describe all 26 issues as code execution, or establish an automatic server compromise without a user interaction.

WebKitGTK and WPE WebKit Security Update: Which Versions Matter?

WebKitGTK’s WSA-2026-0007 lists two issues affecting versions before 2.54.0 and 24 affecting versions before 2.54.3. The 2.54.3 upstream release is the common target for this advisory. Distribution package maintainers may identify their own patched builds, so use the applicable distribution notice when comparing installed packages.

Advisory group Affected upstream versions Patch decision
CVE-2026-112599 and CVE-2026-86922 Before 2.54.0 2.54.0 or later includes these fixes; 2.54.3 also covers the rest of the advisory.
Other 24 listed CVEs Before 2.54.3 Update to 2.54.3 or verify an applicable patched distribution build.

CVE-2026-112623 and CVE-2026-112626 are two use-after-free issues in the second group. WebKitGTK says crafted web content may lead to arbitrary code execution. It describes improved memory management as the fix, without publishing an attack sequence in this advisory.

The advisory also describes CVE-2026-113897 as a possible escape from the Web Content sandbox by a remote attacker. It says the vulnerable code was removed. This is a separate impact description; the advisory does not claim that every listed CVE produces a sandbox escape.

How Should Teams Roll Out the Fix?

Inventory systems and applications that depend on WebKitGTK or WPE WebKit, including embedded web views where those libraries are packaged. Match each installed library and distribution package against its vendor’s security update. Then prioritize environments that render web content from untrusted sources.

A vulnerability intelligence platform can help teams place the advisory beside the actual software inventory. The key decision here is whether a maintained package carries the relevant fix. A version number alone may not show a distribution backport.

Patch and verify the affected libraries
  • Identify installationsRecord WebKitGTK and WPE WebKit library packages and the applications that load them.
  • Apply fixesInstall upstream 2.54.3 or the distribution’s security package for each affected environment.
  • Verify deploymentConfirm package release details and restart applications or services that still load the older library.
  • Track exceptionsAssign an owner and deadline to systems awaiting a compatible package.

These are our rollout recommendations based on the upstream affected-version list. Use a vulnerability management workflow to record package evidence and retest after restart. The upstream project recommends the latest stable WebKitGTK and WPE WebKit releases.

Plan the rollout around the advisory’s affected versions and possible impacts. In patch management, retain the installed package version, distributor notice and post-update verification result. Those records make a backported fix distinguishable from an unpatched upstream build.

Frequently Asked Questions

Which WebKitGTK and WPE WebKit version addresses this advisory?

The upstream 2.54.3 release covers all 26 CVEs listed in WSA-2026-0007. Check distribution notices for their corresponding patched packages.

Do all 26 vulnerabilities allow code execution?

No. The advisory describes distinct impacts, including crashes, memory corruption, possible arbitrary code execution for some CVEs, and a possible sandbox escape for CVE-2026-113897.

How can teams confirm the fix in a distribution package?

Compare the installed package release with the distribution’s security notice, then restart dependent applications and record the verified package state.

Sources

  1. WebKitGTK and WPE WebKit Security Advisory WSA-2026-0007, 18 November 2026
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →