How severe is GHSA-p9rq-q46c-g4x6?

GHSA-p9rq-q46c-g4x6 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-p9rq-q46c-g4x6?

GHSA-p9rq-q46c-g4x6 affects the following packages: Magick.NET-Q16-AnyCPU (NuGet), Magick.NET-Q16-HDRI-AnyCPU (NuGet), Magick.NET-Q16-HDRI-OpenMP-arm64 (NuGet), Magick.NET-Q16-HDRI-arm64 (NuGet), Magick.NET-Q16-HDRI-x64 (NuGet), Magick.NET-Q16-HDRI-x86 (NuGet), Magick.NET-Q16-OpenMP-arm64 (NuGet), Magick.NET-Q16-OpenMP-x64 (NuGet), and 9 more. Ecosystems affected: NuGet.

How do I fix GHSA-p9rq-q46c-g4x6?

Update Magick.NET-Q16-AnyCPU to 14.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9rq-q46c-g4x6 is resolved across your whole dependency graph.

How do I detect GHSA-p9rq-q46c-g4x6 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Magick.NET-Q16-AnyCPU. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-p9rq-q46c-g4x6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-p9rq-q46c-g4x6?

O3 pinpoints whether GHSA-p9rq-q46c-g4x6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-p9rq-q46c-g4x6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p9rq-q46c-g4x6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-p9rq-q46c-g4x6?

GHSA-p9rq-q46c-g4x6 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-p9rq-q46c-g4x6?

GHSA-p9rq-q46c-g4x6 is classified as NULL Pointer Dereference (CWE-476). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p9rq-q46c-g4x6 published, and has it been updated?

GHSA-p9rq-q46c-g4x6 was published on June 26, 2026 and was last updated on June 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

MEDIUM severity

GHSA-p9rq-q46c-g4x6

MEDIUM

GHSA-p9rq-q46c-g4x6 is a medium-severity (CVSS 4.3) NULL Pointer Dereference vulnerability in Magick.NET-Q16-AnyCPU. O3 Security confirms whether GHSA-p9rq-q46c-g4x6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

ImageMagick has Null Pointer Dereference caused by the distort operation when passing incorrect arguments

Also known asCVE-2026-53463

Published

Jun 26, 2026

Updated

Jun 26, 2026

Affected

17 pkgs

Patched

17 / 17

Exploits

None indexed

Exploitation data as of Aug 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-p9rq-q46c-g4x6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 356,453 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

17 pkgs affected

.NETMagick.NET-Q16-AnyCPU.NETMagick.NET-Q16-HDRI-AnyCPU.NETMagick.NET-Q16-HDRI-OpenMP-arm64.NETMagick.NET-Q16-HDRI-arm64.NETMagick.NET-Q16-HDRI-x64.NETMagick.NET-Q16-HDRI-x86.NETMagick.NET-Q16-OpenMP-arm64.NETMagick.NET-Q16-OpenMP-x64+9 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

When passing incorrect arguments in the distort operation a null pointer deference will occur.

Affected Packages

17 total 17 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Magick.NET-Q16-AnyCPU`	all versions	14.14.0
.NETNuGet	`Magick.NET-Q16-HDRI-AnyCPU`	all versions	14.14.0
.NETNuGet	`Magick.NET-Q16-HDRI-OpenMP-arm64`	all versions	14.14.0
.NETNuGet	`Magick.NET-Q16-HDRI-arm64`	all versions	14.14.0
.NETNuGet	`Magick.NET-Q16-HDRI-x64`	all versions	14.14.0
.NETNuGet	`Magick.NET-Q16-HDRI-x86`	all versions	14.14.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Magick.NET-Q16-AnyCPU. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update Magick.NET-Q16-AnyCPU to 14.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9rq-q46c-g4x6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-p9rq-q46c-g4x6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-p9rq-q46c-g4x6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When passing incorrect arguments in the distort operation a null pointer deference will occur.

O3 Security · Impact-Aware SCA

Is GHSA-p9rq-q46c-g4x6 in your dependencies?

O3 detects GHSA-p9rq-q46c-g4x6 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works