TODDR vulnerabilities
We track 5 vulnerabilities in TODDR products across 2 products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on July 16, 2026.
Latest TODDR vulnerabilities
- 7.7 High severity
YAML::Syck: Out-of-bounds Read
YAML::Syck versions before 1.47 for Perl allow an out-of-bounds read via an unbounded newline scan in newline_len. In the bundled libsyck newline_len and is_newline dereference the scan pointer, and the following byte for a "\r\n" pair, with no NUL-terminator
- 7.8 High severity
YAML::Syck: Use After Free
YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor. In the bundled libsyck an anchor name allocated by syck_strndup is stored both as node->anchor, freed when the node
- 9.1 Critical severity
YAML::Syck: Out-of-bounds Read
YAML::Syck versions before 1.47 for Perl allow an out-of-bounds read via a signed-char lookup-table index in syck_base64dec. The base64 decoder in the bundled libsyck indexes the 256-entry static table b64_xtable with a signed char, so any !!binary byte >= 0x8
- 7.3 High severity
YAML::Syck: Buffer Underwrite
YAML::Syck versions before 1.38 for Perl has an out-of-bounds read. The base60 (sexagesimal) parsing code in perl_syck.h has a buffer underflow bug in both int#base60 and float#base60 handlers. When processing the leftmost segment of a colon-separated value (e
- 7.3 High severity
YAML::Syck: Heap-based Buffer Overflow
YAML::Syck versions through 1.36 for Perl has several potential security vulnerabilities including a high-severity heap buffer overflow in the YAML emitter. The heap overflow occurs when class names exceed the initial 512-byte allocation. The base64 decoder co