The SVG backend's color_glyph callback re-entered hb_font_paint_glyph() for every COLRv1 PaintColrGlyph, and each re-entry built a fresh COLR paint context whose HB_MAX_GRAPH_EDGE_COUNT and HB_MAX_NESTING_LEVEL counters started over. The limits therefore applied per nested glyph instead of per top-level glyph, so a DAG in which each level references the next one f times was walked f^levels times, letting a sub-2 KB font spin indefinitely; the same per-re-entry depth reset let a crafted font overflow a small thread stack. Return false, as hb-raster and the PDF backend do (and as the COLR and FreeType walkers expect), so the walker paints the nested glyph inline in the same context, where the existing decycler, nesting limit and edge limit bound the whole graph. The color_glyph_depth counter and active_color_glyphs set existed only to guard the re-entry, so they are dropped from hb_vector_paint_t and from create, destroy and clear. A regression test building a 30-level, 3-reference COLR chain in memory is added to test/vector/test-vector-budget.c for both SVG and PDF. Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-YR4RMFWV. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adding tests
test/vector validates hb-vector CLI output by comparing exact stdout with
golden files.
Test file format (data/tests/*.tests)
Each non-empty, non-comment line has 4 semicolon-separated fields:
font-file;options;unicodes;expected-file
font-file: relative to the.testsfile (or absolute path).options: shell-split arguments passed tohb-vector.unicodes: Unicode sequence, using shape-style codepoint format (for exampleU+0061,U+0062,U+0063).expected-file: path to golden output, relative to the.testsfile. This is also used as the TAP test name.
Example:
../../../api/fonts/Roboto-Regular.abc.ttf;--font-size=64;U+0061,U+0062,U+0063;../expected/basic/reuse-svg.svg
Running vector tests
In an in-tree build:
meson test -C build-default -v --suite vector
Updating expected output
Regenerate a golden file with the current hb-vector binary and replace the
file under data/expected/.
Recording a new test case
Use record-test.sh:
./record-test.sh -o data/tests/basic.tests --test-name reuse-svg ../../build-default/util/hb-vector ../api/fonts/Roboto-Regular.abc.ttf --font-size=64 abc
It subsets the input font, verifies subset-vs-original rendering with
hb-view, stores the subset font under ../fonts/<sha1>.ttf (relative to the target
.tests file), writes expected output under
../expected/<tests-stem>/<test-name>.<ext> by default (unless
--expected-dir or --expected-file is provided), and
appends one test line to the target .tests file. hb-shape, hb-view, and
hb-subset are resolved as sibling executables next to the provided
hb-vector binary. The emitted test line uses Unicode codepoint input in the
unicodes field.