Skip to content
Fencer Vulns
medium 6.5

CVE-2019-9904 json

An issue was discovered in lib\cdt\dttree.c in libcdt.a in graphviz 2.40.1.

published 2019-03-21 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-19259

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

Summary

An issue was discovered in lib\cdt\dttree.c in libcdt.a in graphviz 2.40.1. Stack consumption occurs because of recursive agclose calls in lib\cgraph\graph.c in libcgraph.a, related to agfstsubg in lib\cgraph\subg.c.

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-2019-9904 updated cvss 2.9

graphviz: recursive function call in agclose in lib\cgraph\graph.c causing stack consumption

  • Red Hat Enterprise Linux 6 graphviz, graphviz-gd, graphviz-lua, graphviz-php, graphviz-tcl, graphviz-java, +5 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 graphviz, graphviz-gd, graphviz-lua, graphviz-php, graphviz-tcl, graphviz-java, +6 more Red Hat Enterprise Linux 8 graphviz, graphviz-gd, graphviz-python3
    affected: no fix available “Fix deferred”

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.69% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • gitlab.com https://gitlab.com/graphviz/graphviz/issues/1512 referenced PoC, tagged "exploit" by a source, unverified
  • research.loginsoft.com https://research.loginsoft.com/bugs/stack-buffer-overflow-in-function-agclose-graphviz/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/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 Vulns 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.