Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

Pillow: Invalid free in FreeType glyph rendering when a stroker is active

CVE-2026-112893GHSA-j4m9-6w36-pw47

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pillow 13.0.0; pillow 13.0.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Bitnami pillow

    Affected
    >= 10.0.0, < 13.0.0
    Fixed in
    13.0.0

  • PyPI pillow

    Affected
    >= 10.0.0, < 13.0.0
    Fixed in
    13.0.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-112893: 0.55% estimated exploitation activity in the next 30 days; percentile 46.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary When text is drawn with a non-zero stroke width, Pillow creates a FreeType stroker and then loads each glyph. If `FT_Load_Glyph` fails for a glyph, the cleanup path calls `FT_Done_Glyph` on the `glyph` variable. That variable is not initialized before the first measurement loop, and in the render loop it is not reset to NULL after each glyph is freed. A malformed font loaded from untrusted bytes can force the load error and reach this free. This is a latent memory-safety defect; whether it crashes depends on the value in the uninitialized or stale pointer.

Details `glyph` is declared without a NULL initializer: - `src/_imagingft.c:848` The first measurement loop can jump to `glyph_error` before `glyph` is ever assigned: - `src/_imagingft.c:1010-1013` In the render loop the glyph is freed at the end of each iteration and not set back to NULL: - `src/_imagingft.c:1242` The cleanup frees it whenever a stroker exists: - `src/_imagingft.c:1253-1256` `ImageFont.truetype`…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 7 · amended ·

    Amended from osv record BIT-pillow-2026-112893

  2. Revision 6 · amended ·

    Amended from ghsa record GHSA-j4m9-6w36-pw47

  3. Revision 5 · amended ·

    Amended from osv record BIT-pillow-2026-112893

  4. Revision 4 · amended ·

    Amended from osv record GHSA-j4m9-6w36-pw47

  5. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  6. Revision 2 · amended ·

    Amended from osv record GHSA-j4m9-6w36-pw47

  7. Revision 1 · created ·

    Published from ghsa record GHSA-j4m9-6w36-pw47

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-112893

Advisory: Pillow: Invalid free in FreeType glyph rendering when a stroker is active
IDs: CVE-2026-112893, GHSA-j4m9-6w36-pw47
Record: https://patchnext.com/advisories/cve-2026-112893 (revision 7, source checked 30 Oct 2026, 07:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pillow 13.0.0; pillow 13.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami pillow: affected >= 10.0.0, < 13.0.0; fixed in 13.0.0
- PyPI pillow: affected >= 10.0.0, < 13.0.0; fixed in 13.0.0

## Suggested inspection (read-only)
- Bitnami pillow: check the installed version with your package manager.
- `python -m pip show pillow`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pillow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j4m9-6w36-pw47 (GitHub-reviewed advisory GHSA-j4m9-6w36-pw47 lists affected ranges: PyPI pillow >=10.0.0 <13.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-j4m9-6w36-pw47 (OSV record GHSA-j4m9-6w36-pw47 lists affected ranges: PyPI pillow >=10.0.0 <13.0.0 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-pillow-2026-112893 (OSV record BIT-pillow-2026-112893 lists affected ranges: Bitnami pillow >=10.0.0 <13.0.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…