CVE-2026-13713
MEDIUMDescription
YAML::Syck versions before 1.47 for Perl allow a use-after-free and double-free via an anchor node freed while still on the parser value stack. In the bundled libsyck, when an anchor name is redefined or removed, syck_hdlr_add_anchor and syck_hdlr_remove_anchor free the node stored under that name with syck_free_node. That node can still be live on the parser's value stack, so syck_hdlr_add_node reaches it again and frees it a second time. On a normal build the 48-byte node chunk is freed twice and the interpreter aborts. Anchors need no special flags, so this is reached on the default Load path, and a 7-byte document that redefines an anchor triggers it. Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor mid-parse crashes the interpreter, a denial of service.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 3% of all known CVEs.
References
Related Vulnerabilities
Other CWE-415 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-25136 | Medium | 6.5 | 90% | - | Fix |
| CVE-2003-0545 | Critical | 9.8 | 87% | - | Fix |
| CVE-2018-0101 | Critical | 10.0 | 87% | - | Fix |
| CVE-2026-33824 | Critical | 9.8 | 73% | KEV | Fix |
| CVE-2019-3829 | Medium | 5.3 | 59% | - | Fix |
| CVE-2021-3407 | Medium | 5.5 | 50% | - | Fix |
Common questions
How do I fix CVE-2026-13713?
Upgrade libyaml-syck-perl on debian 11 to 1.34-1+deb11u2 or later.
Is CVE-2026-13713 being actively exploited?
Not that we know of. CVE-2026-13713 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.13% is the estimated probability that it will be exploited in the next 30 days. That is higher than 3% of all scored CVEs.
How severe is CVE-2026-13713?
CVE-2026-13713 has a CVSS v3 base score of 6.2, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-13713 affect?
Published advisories record a fix for libyaml-syck-perl (Debian). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-13713
Markdown
[](https://tridentstack.com/cve/CVE-2026-13713)HTML
<a href="https://tridentstack.com/cve/CVE-2026-13713"><img src="https://tridentstack.com/cve/badge/CVE-2026-13713.svg" alt="CVE-2026-13713"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-17.