What is GHSA-2MHW-8QCG-GR96?

GHSA-2MHW-8QCG-GR96 is a high-severity out-of-bounds write vulnerability in skia-python (pip), affecting versions = 144.0. It is fixed in 144.0.post1. A write operation targets a memory location beyond the intended buffer boundary.

How severe is GHSA-2MHW-8QCG-GR96?

GHSA-2MHW-8QCG-GR96 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of skia-python are affected by GHSA-2MHW-8QCG-GR96?

skia-python (pip) versions = 144.0 is affected.

Is there a fix for GHSA-2MHW-8QCG-GR96?

Yes. GHSA-2MHW-8QCG-GR96 is fixed in 144.0.post1. Upgrade to this version or later.

Is GHSA-2MHW-8QCG-GR96 exploitable, and should I be worried?

Whether GHSA-2MHW-8QCG-GR96 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-2MHW-8QCG-GR96 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-2MHW-8QCG-GR96?

Upgrade skia-python to 144.0.post1 or later.

GHSA-2MHW-8QCG-GR96 in skia-python | Intelligent Application Security

Summary

Workarounds

Users must upgrade the wheel package after release.

References

Impact

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

GHSA-2MHW-8QCG-GR96 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (144.0.post1); upgrading removes the vulnerable code path.

Affected versions

skia-python (= 144.0) skia-python (<= 138.0)

Security releases

skia-python → 144.0.post1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

In the case of skia-python, the solution is to explicitly install freetype in the build process and rebuild the wheels.

The original report was suggesting the above, but in the current build_Linux.sh script, the patched freetype-devel version 2.9.1-10 gets installed as a dependency. It's just that we need to rebuild the wheel for a new release.

Frequently Asked Questions

What is GHSA-2MHW-8QCG-GR96? GHSA-2MHW-8QCG-GR96 is a high-severity out-of-bounds write vulnerability in skia-python (pip), affecting versions = 144.0. It is fixed in 144.0.post1. A write operation targets a memory location beyond the intended buffer boundary.
How severe is GHSA-2MHW-8QCG-GR96? GHSA-2MHW-8QCG-GR96 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of skia-python are affected by GHSA-2MHW-8QCG-GR96? skia-python (pip) versions = 144.0 is affected.
Is there a fix for GHSA-2MHW-8QCG-GR96? Yes. GHSA-2MHW-8QCG-GR96 is fixed in 144.0.post1. Upgrade to this version or later.
Is GHSA-2MHW-8QCG-GR96 exploitable, and should I be worried? Whether GHSA-2MHW-8QCG-GR96 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-2MHW-8QCG-GR96 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-2MHW-8QCG-GR96? Upgrade skia-python to 144.0.post1 or later.