CVE-2026-49219 medium CVSS 5.5

Information Disclosure in Magick.NET-Q16-AnyCPU (CVE-2026-49219)

Summary

Vulnerability in Magick.NET-Q16-AnyCPU (CVE-2026-49219). Confidential information can be exposed externally. Mitigation: upgrade to 14.14.0 or later.

Original description

The description as published by the source.

An incorrect parsing of the filename can result in a policy bypass and read files disallowed by a security policy using a symlink.

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-49219 has been found in Magick.NET-Q16-AnyCPU.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade Magick.NET-Q16-AnyCPU to 14.14.0 or later.
If unsure, ask your IT team or search "Magick.NET-Q16-AnyCPU CVE-2026-49219" on the vendor's site.

CVE-2026-49219 (Magick.NET-Q16-AnyCPU) — CWE-200 / CVSS v3 5.5
Attack vector: local / no user interaction
Patched: 14.14.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

Information disclosure (CWE-200) exists in Magick.NET-Q16-AnyCPU.

📍 Affected scope

Check the vendor advisory for the affected versions of Magick.NET-Q16-AnyCPU.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 14.14.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 'Magick.NET-Q16-AnyCPU' . 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
Identify exposure identify
```
grep -r 'Magick.NET-Q16-AnyCPU' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Magick.NET-Q16-AnyCPU を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade Magick.NET-Q16-AnyCPU to 14.14.0
```
ステージング環境で 14.14.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。