Algorithm::UrataniTakeda versions from 0.1.5 before 0.1.7 for Perl allow memory exhaustion via a never-cleared failure shift cache in search
Affects Algorithm::UrataniTakeda 0.1.5 and 0.1.6 when a long-lived matcher object runs many searches, because its failure shift cache grows without limit. Fixed in 0.1.7.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 0.1.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
Algorithm::UrataniTakeda versions from 0.1.5 before 0.1.7 for Perl allow memory exhaustion via a never-cleared failure shift cache in search. The failure shift is cached for each pair of trie state and text character in a field of the matcher object, and nothing clears it. A character not seen before at a given state adds an entry that lasts for the life of the matcher. An attacker who can submit text with many distinct characters to a long-lived matcher can grow its memory with each search.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Algorithm-UrataniTakeda
From 0.1.5 · fixed in 0.1.7
References 3
GitHub · robrwo/perl-Algorithm-UrataniTakeda
Questions about CVE-2026-113811
What does this mean?
Each search run on a long-lived matcher object adds an entry to its failure shift cache, and that cache is never cleared. Over time the cache keeps growing and can exhaust the memory of the process running the matcher.Source: github.com, github.com
Am I affected, and how do I check?
Versions 0.1.5 and 0.1.6 of Algorithm::UrataniTakeda for Perl are affected, and the growth only happens when a matcher object is kept alive across many searches. To check the installed version, run perl -MAlgorithm::UrataniTakeda -e 'print $Algorithm::UrataniTakeda::VERSION'.Source: github.com, github.com
What should I do about it?
Upgrade Algorithm::UrataniTakeda to version 0.1.7, which is the first version listed as fixed.Source: github.com, github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data