| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $5k-$25k | 0.00 |
Summary
A vulnerability has been found in Apple Safari up to 15.0 and classified as critical. This affects an unknown part of the component WebKit. The manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2021-30936. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, has been found in Apple Safari up to 15.0 (Web Browser). This issue affects an unknown part of the component WebKit. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 12/14/2021 by Chijin Zhou as HT212982 as confirmed advisory (Website). The advisory is shared at support.apple.com. The identification of this vulnerability is CVE-2021-30936. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/07/2026). The advisory points out:
Processing maliciously crafted web content may lead to arbitrary code execution
The vulnerability scanner Nessus provides a plugin with the ID 241427 (RHEL 7 : webkitgtk4 (RHSA-2025:10364)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 15.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
A use after free issue was addressed with improved memory management.
The vulnerability is also documented in the databases at Tenable (241427) and CERT Bund (WID-SEC-2026-0631). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Apple macOS
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.apple.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 241427
Nessus Name: RHEL 7 : webkitgtk4 (RHSA-2025:10364)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Safari 15.2
Timeline
04/13/2021 🔍12/14/2021 🔍
12/14/2021 🔍
12/17/2021 🔍
03/07/2026 🔍
Sources
Vendor: apple.comAdvisory: HT212982
Researcher: Chijin Zhou
Status: Confirmed
CVE: CVE-2021-30936 (🔍)
GCVE (CVE): GCVE-0-2021-30936
GCVE (VulDB): GCVE-100-188597
CERT Bund: WID-SEC-2026-0631 - Apple macOS: Mehrere Schwachstellen
Entry
Created: 12/17/2021 16:58Updated: 03/07/2026 10:12
Changes: 12/17/2021 16:58 (19), 12/17/2021 17:01 (27), 12/23/2021 12:46 (1), 07/10/2025 20:36 (16), 03/07/2026 10:12 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.

No comments yet. Languages: en.
Please log in to comment.