| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Apple Safari. It has been classified as critical. This vulnerability affects unknown code of the component Web Handler. This manipulation causes memory corruption. The identification of this vulnerability is CVE-2025-31223. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Apple Safari (unknown version). It has been declared as critical. Affected by this vulnerability is an unknown code block of the component Web Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The issue was addressed with improved checks. This issue is fixed in watchOS 11.5, tvOS 18.5, iOS 18.5 and iPadOS 18.5, macOS Sequoia 15.5, visionOS 2.5, Safari 18.5. Processing maliciously crafted web content may lead to memory corruption.
The advisory is shared at support.apple.com. This vulnerability is known as CVE-2025-31223 since 03/27/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 04/01/2026).
The vulnerability scanner Nessus provides a plugin with the ID 304374 (SUSE SLES12 Security Update : webkit2gtk3 (SUSE-SU-2026:1139-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (304374) and EUVD (EUVD-2025-14642). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
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: Memory corruptionCWE: 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: 304374
Nessus Name: SUSE SLES12 Security Update : webkit2gtk3 (SUSE-SU-2026:1139-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
03/27/2025 CVE reserved05/13/2025 Advisory disclosed
05/13/2025 VulDB entry created
04/01/2026 VulDB entry last update
Sources
Vendor: apple.comAdvisory: support.apple.com
Status: Confirmed
CVE: CVE-2025-31223 (🔒)
GCVE (CVE): GCVE-0-2025-31223
GCVE (VulDB): GCVE-100-308509
EUVD: 🔒
Entry
Created: 05/13/2025 07:55Updated: 04/01/2026 01:04
Changes: 05/13/2025 07:55 (54), 05/14/2025 14:41 (1), 05/28/2025 10:49 (1), 04/01/2026 01:04 (2)
Complete: 🔍
Cache ID: 216:D67: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.