Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107381 medium CVSS 6.5

Vulnerability in enshrined/svg-sanitize (CVE-2026-107381)

Summary

Vulnerability in enshrined/svg-sanitize (CVE-2026-107381). Risk of unauthorized operations or information disclosure. Exploitable via HrEf. Mitigation: upgrade to 1.0.0 or later.

Original description

The description as published by the source.

Summary

Resolver::processReferences() collects elements with the XPath predicate `use[@href or @xlink:href]`, which is case sensitive. A element written as xlink:HrEf is therefore never added to the reference graph, so the nesting-DoS nullification never marks it for removal. Sanitizer::cleanHrefAttributes() then runs later in the same pass and rewrites xlink:HrEf back to the canonical xlink:href. The sanitizer hands back a fully live nesting bomb that it would have stripped completely had the input used canonical casing.

This is the mirror image of CVE-2025-55166: that fix made href value checking case insensitive, but the `` reference graph still selects nodes case sensitively.

Where it is

src/ElementReference/Resolver.php:97-118, the case-sensitive node selection:

$useNodeName = $this->xPath->createNodeName('use');
foreach ($this->subjects as $subject) {
    $useElements = $this->xPath->query(
        $useNodeName . '[@href or @xlink:href]',
        $subject->getElement()
    );

src/Sanitizer.php:479-504, the normalization that happens afterwards and makes the attribute live again:

// in case the attribute name is `HrEf`/`xlink:HrEf`, adjust it to `href`/`xlink:href`
if (!in_array($attribute->nodeName, $this->allowedAttrs, true)
    && in_array(strtolower($attribute->nodeName), $this->allowedAttrs, true)
) {
    $element->removeAttribute($attribute->nodeName);
    $element->setAttribute(strtolower($attribute->nodeName),…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-107381 has been found in enshrined/svg-sanitize.
Attackers can target a specific entry point like HrEf over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade enshrined/svg-sanitize to 1.0.0 or later.
If unsure, ask your IT team or search "enshrined/svg-sanitize CVE-2026-107381" on the vendor's site.

CVE-2026-107381 (enshrined/svg-sanitize) — CWE-178 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: HrEf / href / useNestingLimit / useDosTest.svg
Patched: 1.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-178) exists in enshrined/svg-sanitize. Attackers reach the vulnerable code path via HrEf without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of enshrined/svg-sanitize. Attack surface: HrEf / href / useNestingLimit / useDosTest.svg.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.0.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'enshrined/svg-sanitize' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'enshrined/svg-sanitize' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で enshrined/svg-sanitize を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade enshrined/svg-sanitize to 1.0.0

    ステージング環境で 1.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer enshrined/svg-sanitize
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0"}]}]
Packagist enshrined/svg-sanitize
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details