CVE-2026-16634
- Published24 Jul 2026
Description
TOML::XS versions before 0.06 for Perl bundle an unsupported and vulnerable version of tomlc99. The tomlc99 library is no longer maintained, and has an uncontrolled recursion vulnerability publicly reported in the issue tracker. Any caller that passes untrusted TOML to from_toml risks a stack overflow from a deeply-nested document. TOML::XS version 0.06 or later uses the successor tomlc17 library.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://github.com/cktan/tomlc17
- https://github.com/cktan/tomlc99/issues/97
- https://metacpan.org/release/FELIPE/TOML-XS-0.06/changes
- https://raw.githubusercontent.com/cktan/tomlc99/29076dfd095bbbbd50a3c1b2760d29f4b83e74ac/README.md
- https://toml.io/en/v1.0.0
- http://www.openwall.com/lists/oss-security/2026/07/24/4
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-16634 being actively exploited?
CVE-2026-16634 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.82%.
How severe is CVE-2026-16634?
CVE-2026-16634 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.82% probability of exploitation.
How do I fix CVE-2026-16634?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-16634 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.