GHSA-2mhw-8qcg-gr96 json
skia-python vendors vulnerable libfreetype because of pinned cibuildwheel version
published 7mo ago modified 7mo ago
- cvss
- 8.1
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact
The Linux wheels for skia-python vendor a vulnerable version of libfreetype that is affected by CVE-2025-27363 [1].
The root cause is a chain of unfortunate events:
1. skia-python builds wheels using pinned pypa/cibuildwheel@2.21.3 [2]
2. cibuildwheel 2.21.3 in turn pins manylinux container images [3]
3. In these images, version 2.9.1-9.el8 of RedHat package freetype is *preinstalled*. This package version is vulnerable and has since been patched in 2.9.1-10.
4. During the skia-python Linux build, libfreetype is vendored from the system, resulting in skia-python.libs/libfreetype-29a7443c.so.6.16.1
[ To find the provenance of your vendored libfreetype, we extracted the 8-character hash of the original binary file that is added during the build process (29a7443c), and matched it against our database of hashes all historic Red Hat, Debian and Ubuntu releases of freetype. ]
5. Because freetype is only a *transitive* dependency of the packages explicitly installed by the build script [4], it is not upgraded to the patched version [4].
5. As a result, the published wheels embed a vulnerable libfreetype, even though patched packages are available upstream.
This appears to be a broader manylinux ecosystem issue. The base images do not enforce that `yum update` runs on container start, so preinstalled libraries may remain vulnerable indefinitely.
### Patches
> 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.
### Workarounds
Users must upgrade the wheel package after release.
### References
1. https://nvd.nist.gov/vuln/detail/CVE-2025-27363 2. https://github.com/kyamagu/skia-python/blob/9ffb045811f9b5508e152302d5b81aadca6edd8d/.github/workflows/ci.yml#L38 3. https://github.com/pypa/cibuildwheel/blob/v2.21.3/cibuildwheel/resources/pinned_docker_images.cfg 4. https://github.com/kyamagu/skia-python/blob/9ffb045811f9b5508e152302d5b81aadca6edd8d/scripts/build_Linux.sh#L6
Patch / fix
- pypi skia-python 144.0.post1
Is GHSA-2mhw-8qcg-gr96 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | skia-python | 1 listed version <144.0.post1 |
144.0.post1 |
Classification
References
Sources
- GitHub Advisory GHSA-2mhw-8qcg-gr96
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.