Skip to content
Fencer Intel
high 8.8

CVE-2020-5496 json

FontForge 20190801 has a heap-based buffer overflow in the Type2NotDefSplines() function in splinesave.c.

published 6y ago modified 4mo ago also EUVD-2020-26663

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

FontForge 20190801 has a heap-based buffer overflow in the Type2NotDefSplines() function in splinesave.c.

Patch / fix

  • fontforge Debian 14, Debian 13, Debian 12 1:20201107~dfsg-1

debian advisories DEBIAN-CVE-2020-5496

  • fontforge SLE Software Development Kit 12 SP5, SLE Software Development Kit 12 SP4 20170731-11.11.1

suse advisories SUSE-SU-2020:0393-1

  • fontforge openSUSE Leap 15.1 20170731-lp151.4.3.1

opensuse advisories openSUSE-SU-2020:0089-1

Is CVE-2020-5496 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-5496 updated cvss 5.5

fontforge: heap-based buffer overflow in the Type2NotDefSplines() function in splinesave.c

  • Red Hat Enterprise Linux 6 fontforge Red Hat Enterprise Linux 7 fontforge Red Hat Enterprise Linux 8 fontforge
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.37% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/fontforge/fontforge/issues/4085 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

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.