darylldoyle svg-sanitizer up to 0.x Sanitization src/Sanitizer.php cleanAttributesOnWhitelist double free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 1.85- |
Summary
A vulnerability classified as problematic was found in darylldoyle svg-sanitizer up to 0.x. The affected element is the function cleanAttributesOnWhitelist of the file src/Sanitizer.php of the component Sanitization. Such manipulation leads to double free.
This vulnerability is referenced as CVE-2026-107379. It is possible to launch the attack remotely. No exploit is available.
Upgrading the affected component is advised.
Details
A vulnerability was found in darylldoyle svg-sanitizer up to 0.x. It has been rated as problematic. Affected by this issue is the function cleanAttributesOnWhitelist of the file src/Sanitizer.php of the component Sanitization. The manipulation with an unknown input leads to a double free vulnerability. Using CWE to declare the problem leads to CWE-415. The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. Impacted is availability. CVE summarizes:
savg-sanitizer is a PHP SVG/XML sanitizer. Prior to 1.0.0, svg-sanitizer allows a crafted SVG DTD with a #FIXED attribute default to make cleanAttributesOnWhitelist() perform a double DOMElement::removeAttribute() call on the same attribute name in src/Sanitizer.php. The first removal deletes the explicit attribute, while the DTD default rematerializes the value before the href safety path performs the second removal, which can corrupt libxml state and terminate the PHP worker. An attacker who can submit SVG content to a sanitization endpoint can repeatedly interrupt workers and degrade or exhaust application availability. This issue is fixed in version 1.0.0.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-107379 since 10/07/2026. The exploitation is known to be easy. The attack may be launched remotely. There are known technical details, but no exploit is available.
By approaching the search of inurl:src/Sanitizer.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.0.0 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒
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: Double freeCWE: CWE-415 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: svg-sanitizer 1.0.0
Timeline
10/07/2026 CVE reserved10/08/2026 Advisory disclosed
10/08/2026 VulDB entry created
10/08/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-107379 (🔒)
GCVE (CVE): GCVE-0-2026-107379
GCVE (VulDB): GCVE-100-415520
Entry
Created: 10/08/2026 20:33Changes: 10/08/2026 20:33 (66)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.