Skip to content
Fencer Intel
medium 5.5

CVE-2019-9754 json

An issue was discovered in Tiny C Compiler (aka TinyCC or TCC) 0.9.27.

published 2019-03-13 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-19117

cvss
5.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

An issue was discovered in Tiny C Compiler (aka TinyCC or TCC) 0.9.27. Compiling a crafted source file leads to an 1 byte out of bounds write in the end_macro function in tccpp.c.

Patch / fix

  • tcc Debian 13, Debian 12 0.9.27+git20200814.62c30a4a-1

debian advisories DEBIAN-CVE-2019-9754

Exploit prediction

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

Exploits and checks

  • lists.nongnu.org https://lists.nongnu.org/archive/html/tinycc-devel/2019-03/msg00038.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/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.