CVE-2026-45358 medium CVSS 5.3

Out-of-Bounds Read in Magick.NET-Q16-AnyCPU (CVE-2026-45358)

Summary

Vulnerability in Magick.NET-Q16-AnyCPU (CVE-2026-45358). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 14.13.1 or later.

Original description

The description as published by the source.

An of by one in the meta encoder could result in an out of bounds read of a single byte in the meta encoder.

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-45358 has been found in Magick.NET-Q16-AnyCPU.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade Magick.NET-Q16-AnyCPU to 14.13.1 or later.
If unsure, ask your IT team or search "Magick.NET-Q16-AnyCPU CVE-2026-45358" on the vendor's site.

CVE-2026-45358 (Magick.NET-Q16-AnyCPU) — CWE-125 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 14.13.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

Out-of-bounds read (CWE-125) 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.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 14.13.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 '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.13.1
```
ステージング環境で 14.13.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。