CVE-2024-43091: WebKitGTK Integer Overflow

Publish date: October 1, 2026
Severity
Critical
CVSS score
9.8
Package
libwebkit2gtk-4.1-0
Affected versions

CVE-2024-43091 is a critical integer overflow vulnerability in WebKitGTK, published in the National Vulnerability Database (NVD) on November 13, 2024. It carries a CVSS v3.1 base score of 9.8 (Critical). According to its CVSS vector, it can be exploited over the network, needs no privileges and no user interaction.

What is CVE-2024-43091?

An out-of-bounds write in SkEmbossMaskFilter.cpp can lead to remote code execution.

The NVD description reads:

In filterMask of SkEmbossMaskFilter.cpp, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

NVD maps this issue to CWE-190 (Integer Overflow or Wraparound), CWE-787 (Out-of-bounds Write).

Affected versions and packages

NVD does not publish structured version ranges for CVE-2024-43091 at the time of writing, so check the description above and the vendor advisory in the references for the exact affected releases.

Note: the product named in the NVD CPE data for CVE-2024-43091 (Google Chrome, Android or golang.org/x/net) differs from the package Echo's advisory data tracks, so the upstream fixed versions above do not map directly to the tracked package. Verify the fixed version against your distribution's or vendor's advisory.

Echo's advisory data tracks 2 packages for CVE-2024-43091: libjavascriptcoregtk-4.1-0, libwebkit2gtk-4.1-0.

Package versions listed in Echo's advisory data for this CVE (compare them with the versions you run):

  • libjavascriptcoregtk-4.1-0, libwebkit2gtk-4.1-0: 2.52.5-1~deb13u1, 2.52.6-1~deb13u1

Severity and CVSS score

  • CVSS v3.1 (NVD): 9.8 Critical, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • EPSS (FIRST, scored November 3, 2026): 0.73% probability of exploitation activity in the next 30 days, 54th percentile
  • Weaknesses: CWE-190 (Integer Overflow or Wraparound), CWE-787 (Out-of-bounds Write)

A score of 9.8 puts CVE-2024-43091 in the Critical range (9.0 to 10.0), the highest CVSS band. The vector shows the attack path and the impact on confidentiality, integrity and availability. For help weighing exploit likelihood against raw severity, see our guide to open source vulnerability scanning.

Impact: Integer Overflow

The CVSS vector rates the impact on confidentiality as high, integrity as high and availability as high. Exploitation requires no privileges and no user interaction, and the attacker reaches the target over the network.

What this means in practice depends on how WebKitGTK is used in your environment: how widely it is deployed, whether the affected code path is reachable, and what the process can access. Treat the exposed systems that run a listed version as in scope until you have confirmed otherwise.

Is CVE-2024-43091 being exploited in the wild?

Known exploitation: CISA KEV

No. As of November 4, 2026, CVE-2024-43091 is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog (catalog version 2026.11.03). KEV only lists vulnerabilities with confirmed exploitation, so absence from the catalog is not proof that nobody is exploiting the flaw.

EPSS score and percentile

The Exploit Prediction Scoring System (EPSS) from FIRST estimates the probability that a CVE will see exploitation activity in the next 30 days. On November 3, 2026, CVE-2024-43091 had an EPSS score of 0.007, which corresponds to a probability of 0.73%. It sits at the 54th percentile, which means it is scored as more likely to be exploited than roughly 54% of scored CVEs, placing it above the median of scored CVEs. EPSS is recalculated daily and is a likelihood estimate, not a confirmation, so read it together with KEV status, exposure and CVSS severity.

Attack vector, complexity, privileges and user interaction

Based on the CVSS v3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (source: NVD), this is how an attacker has to approach CVE-2024-43091:

  • Attack vector: Network (AV:N): the flaw can be reached remotely over the network, so the attacker does not need to be on the same host or LAN.
  • Attack complexity: Low (AC:L): no special conditions are needed, so the attack can be repeated reliably.
  • Privileges required: None (PR:N): no account or credentials are needed.
  • User interaction: None (UI:N): no action by a user is required.
  • Scope: Unchanged (S:U): the impact stays within the security scope of the vulnerable component.

Is there a public proof of concept or exploit?

CISA's SSVC assessment recorded in NVD (dated December 4, 2024) lists the exploitation status as "none", which means there was no evidence of active exploitation and no public proof of concept at that time. None of the references in the NVD record is tagged as an exploit. This reflects NVD and CISA records as of November 4, 2026, and public exploit code can appear at any time.

Practical exposure conditions

  • Only systems that run an affected version are exposed. Compare the WebKitGTK versions in your hosts and container images against the versions listed in the Echo advisory data and the vendor advisory above.
  • The vector is network-based, so WebKitGTK deployments that process input from untrusted networks carry the most risk, especially internet-facing ones. Internal-only deployments are still exposed to anyone who can reach them.
  • No credentials are needed, so exposure does not depend on how well accounts are protected.
  • No user has to click or open anything, so the flaw can be triggered without any user action.
  • CISA's SSVC assessment marks the issue as not automatable, which means attacks are harder to run at scale.

How to fix CVE-2024-43091

  1. Inventory. Find every host, container image and base image that includes WebKitGTK, including the packages listed above (libjavascriptcoregtk-4.1-0, libwebkit2gtk-4.1-0).
  2. Upgrade. Upgrade to the release that the vendor or your distribution lists as fixed for CVE-2024-43091. The references below link to the upstream advisory.
  3. Rebuild and restart. Rebuild container images and restart the services that load WebKitGTK so the patched code is actually used.
  4. Verify. Re-scan your images and hosts to confirm that no package still matches a vulnerable version of CVE-2024-43091.

Interim mitigations if you cannot patch immediately

These are general hardening steps, not a vendor-specific workaround. Updating is the only complete fix.

  • Restrict network access to services that use WebKitGTK to trusted sources with firewall rules or allow-lists until you can patch.
  • Monitor logs and runtime behavior on affected systems for unusual activity, and prioritize them in your next patch window.

How Echo helps with CVE-2024-43091

Echo is a registered CVE Numbering Authority (CNA) and ships patched, vetted open source packages and container images, so teams can remove vulnerable components instead of tracking an endless backlog. For this CVE, Echo's advisory data tracks 2 packages (libjavascriptcoregtk-4.1-0, libwebkit2gtk-4.1-0). Read how automated patch SLAs reduce enterprise risk in how automated patch SLAs reduce enterprise risk and why how to deal with CVE backlogs matters. Related WebKitGTK advisories: CVE-2024-1283 and CVE-2026-6296.

Frequently asked questions about CVE-2024-43091

What is CVE-2024-43091?

CVE-2024-43091 is a critical integer overflow vulnerability in WebKitGTK. An out-of-bounds write in SkEmbossMaskFilter.cpp can lead to remote code execution. It has a CVSS base score of 9.8.

Which versions are affected by CVE-2024-43091?

NVD does not publish structured version ranges for it yet. Echo's advisory data tracks these WebKitGTK packages: libjavascriptcoregtk-4.1-0, libwebkit2gtk-4.1-0.

Is CVE-2024-43091 actively exploited?

It is not listed in CISA's KEV catalog as of November 4, 2026 (catalog version 2026.11.03), but that does not rule out exploitation. FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 0.73%, at the 54th percentile (November 3, 2026). On public exploit code: CISA's SSVC assessment in NVD (dated December 4, 2024) lists no public proof of concept.

How do I fix CVE-2024-43091?

Upgrade to the release that the vendor or your distribution lists as fixed for CVE-2024-43091. The references below link to the upstream advisory. Then rebuild images, restart affected services and re-scan to confirm the fix.

How severe is CVE-2024-43091?

It is rated Critical with a CVSS base score of 9.8. The vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H means it can be exploited over the network, with no privileges and no user interaction.

Are there other WebKitGTK vulnerabilities I should patch?

Yes. Echo's advisory data also covers CVE-2024-1283 and CVE-2026-6296. Patch them together to reduce the number of upgrade cycles.