Skip to content
Fencer Intel
high 8.8

CVE-2010-0050 in the critical feed json

Use-after-free vulnerability in WebKit in Apple Safari before 4.0.5 allows remote attackers to execute arbitrary code or cause a denial of…

published 16y ago modified 4mo ago also EUVD-2010-0082

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
11.6%
EPSS 11.6% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

Use-after-free vulnerability in WebKit in Apple Safari before 4.0.5 allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via an HTML document with improperly nested tags.

Patch / fix

  • apple safari 4.0.5
  • apple iphone_os 4.0

Is CVE-2010-0050 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-0050 updated

webkitgtk: multiple security vulnerabilities in WebKit

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-12425)

Exploit prediction

11.64% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-12425 Webkit (Apple Safari 4.0.5) - Blink Tag Stack Exhaustion Denial of Service dos, 2010-04-27

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.