Categories
CVE-2026-58588 medium CVSS 6.1

Cross-Site Scripting (XSS) in drupal/canvas (CVE-2026-58588)

Summary

Cross-site scripting in drupal/canvas (CVE-2026-58588). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.4.2, 1.5.2, 1.6.1, 1.7.1 or later.

Original description

The description as published by the source.

The Canvas module allow you to upload image files via a custom API.

The validation rules check the file extension of the uploaded file but not the file MIME type. This may allow a malicious user to upload a file that is not an image.

Certain web-server configurations may serve the uploaded file with its actual MIME type rather than an image type. This may lead to cross-site scripting (XSS) or other unexpected behavior.

Source: NIST National Vulnerability Database 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-58588 has been found in drupal/canvas.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade drupal/canvas to 1.4.2, 1.5.2, 1.6.1, 1.7.1 or later.
If unsure, ask your IT team or search "drupal/canvas CVE-2026-58588" on the vendor's site.

CVE-2026-58588 (drupal/canvas) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.4.2, 1.5.2, 1.6.1, 1.7.1 — 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

Cross-site scripting (XSS) (CWE-79) exists in drupal/canvas.

📍 Affected scope

Check the vendor advisory for the affected versions of drupal/canvas.

🔥 Severity

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

🔧 How to fix

Update to 1.4.2, 1.5.2, 1.6.1, 1.7.1.

🛡️ 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 'drupal/canvas' . 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 'drupal/canvas' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade drupal/canvas to 1.4.2, 1.5.2, 1.6.1, 1.7.1

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

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

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

Affected packages

Packagist:https://packages.drupal.org/8 drupal/canvas
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2"}],"database_specific":{"constraint":"<1.4.2"}},{"type":"ECOSYSTEM","events":[{"introduced":"1.5.0"},{"fixed":"1.5.2"}],"database_specific":{"constraint":">=1.5.0 <1.5.2"}},{"type":"ECOSYSTEM","events":[{"introduced":"1.6.0"},{"fixed":"1.6.1"}],"database_specific":{"constraint":">=1.6.0 <1.6.1"}},{"type":"ECOSYSTEM","events":[{"introduced":"1.7.0"},{"fixed":"1.7.1"}],"database_specific":{"constraint":">=1.7.0 <1.7.1"}}]

References

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