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.
CVE-2026-107379
MEDIUMPre-NVD 6.56.5ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.5 from GitHub Security Advisory (severity: MODERATE) published 2026-10-08. A secondary CVSS source baseline 6.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-95136 (ENISA EUVD) · GHSA-v383-3rw5-q8rf (GitHub Security Advisories)Source: ENISA EUVD
6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMmedium confidence
- EG Risk
- 45EG Risk 45/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity65% × 45%Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.5%
- EPSS %ILE
- 45th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 8, 2026
Last Modified
October 9, 2026
Advisory Details (3)
Auto-updated Oct 8, 2026Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available
1.0.0
Patch available: darylldoyle/svg-sanitizer 1.0.0
https://github.com/darylldoyle/svg-sanitizer/releases/tag/1.0.0GitHub commit Patch Available
commit 23877db7e76f (darylldoyle/svg-sanitizer)
Patch available: darylldoyle/svg-sanitizer 1.0.0 (contains commit 23877db7e76f)
https://github.com/darylldoyle/svg-sanitizer/commit/23877db7e76f1e1df5c3e65ab30239219c3d2867GitHub advisoryMentions a patch (unverified)
enshrined/svg-sanitize: Denial of Service via DTD Attribute Declaration Crash · Advisory · darylldoyle/svg-sanitizer · GitHub
https://github.com/darylldoyle/svg-sanitizer/security/advisories/GHSA-v383-3rw5-q8rfVendor Advisories for CVE-2026-107379(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| composer | enshrined/svg-sanitize @ 1.0.0 (fixes <= 0.22.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| enshrined/svg-sanitize | 0.1.0 ... 0.9.2 (48 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 33× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.5% · 45th percentile
- 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
- 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-07 19:42 UTCEchelonGraph re-scored
- 2026-11-07 19:42 UTCGHSA enrichmentGHSA-v383-3rw5-q8rf · GitHub severity MODERATE · GitHub CVSS 6.5
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-01 08:00 UTCGHSA enrichmentGHSA-v383-3rw5-q8rf · GitHub severity MODERATE · GitHub CVSS 6.5
- 2026-11-01 08:00 UTCEchelonGraph re-scored
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-31 11:25 UTCOSV refresh
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 29 moreShow fewer
- 2026-10-25 14:54 UTCEchelonGraph re-scored
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-23 08:44 UTCEchelonGraph re-scored
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-18 05:07 UTCEchelonGraph re-scored
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-12 16:38 UTCEchelonGraph re-scored
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-11 20:14 UTCEchelonGraph re-scored
- 2026-10-11 16:40 UTCEchelonGraph re-scored
- 2026-10-11 15:00 UTCEchelonGraph re-scored
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-10 14:37 UTCEchelonGraph re-scored
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-09 12:34 UTCEchelonGraph re-scored
- 2026-10-09 11:54 UTCEchelonGraph re-scored
- 2026-10-08 18:36 UTCEchelonGraph re-scored
- 2026-10-08 18:14 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
- 2026-10-08 18:14 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
6 shownPackagist:enshrined/svg-sanitize
Frequently asked(5)
What is CVE-2026-107379?
CVE-2026-107379 is a medium-severity vulnerability; its CVE record was published on October 8, 2026. 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…
When was the CVE record for CVE-2026-107379 published?
The CVE record for CVE-2026-107379 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-107379 actively exploited?
CVE-2026-107379 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107379?
CVE-2026-107379 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107379?
A fix for CVE-2026-107379 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107379 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107379
Is Your Infrastructure Affected by CVE-2026-107379?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.