Skip to main content
VulnerabilityPublished Updated

CVE-2026-80490: Algorithm-AhoCorasick-XS (Perl module) · Out-of-bounds Read

Affects Algorithm-AhoCorasick-XS (Perl module)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.4 Medium.

Data as of 14 Nov 2026, 20:58 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.14.4
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Algorithm-AhoCorasick-XSAffected
  • <=0.04
Fixed in–
CPANAlgorithm-AhoCorasick-XSpkg:cpan/Algorithm-AhoCorasick-XSOther threatsAffected
  • <=0.04
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should avoid passing numeric or reference types as the haystack input to the matches, first_match, or match_details methods. Validate or sanitize inputs to ensure they are properly stringified before use. Monitor vendor advisories for updates or patches addressing this issue.

Description

Algorithm::AhoCorasick::XS versions up to 0.04 for Perl contain an out-of-bounds read vulnerability due to improper handling of the haystack string length before stringification. This occurs when the input is a reference, integer, or float, causing the length macro to return invalid values and potentially abort the process. The issue arises from the unspecified evaluation order of arguments in the std::string constructor. This vulnerability can be triggered by numeric inputs such as those from decoded JSON or numeric database columns.

References

Community reviews

Loading reviews…