PatchSiren cyber security CVE debrief
CVE-2026-19487 Perl CVE debrief
Perl versions from 5.9.4 before 5.41.9 produce incorrect regular expression match results due to a stale failure flag in the Aho-Corasick prescan. This issue can cause alternation to miss input or match on the wrong branch, leading to incorrect access or filtering decisions. The vulnerability affects systems using these Perl versions, potentially leading to incorrect access or filtering decisions. System administrators and developers should be aware of this issue and take necessary actions to mitigate potential risks. The CVE record and NVD entry provide details on the vulnerability, but further analysis is needed to fully understand the impact and affected systems.
- Vendor
- Perl
- Product
- perl5
- CVSS
- MEDIUM 5.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-13
- Original CVE updated
- 2026-08-28
- Advisory published
- 2026-08-13
- Advisory updated
- 2026-08-28
Who should care
System administrators and developers using Perl versions from 5.9.4 before 5.41.9 should be aware of this vulnerability and take necessary actions to mitigate potential risks. This includes assessing systems for exposure, planning vendor-supported updates or mitigations, reviewing compensating controls, and tracking exceptions. Affected operators, platforms, vulnerability-management teams, and security teams should prioritize this issue due to its potential impact on access and filtering decisions.
Technical summary
The Aho-Corasick prescan in Perl versions from 5.9.4 before 5.41.9 can produce incorrect regular expression match results due to a stale failure flag. This occurs when a failing transition sets the failed flag, and a later successful transition does not clear it, causing the prescan to stop prematurely. As a result, alternation may miss input it should match or match it on the wrong branch, leading to incorrect access or filtering decisions.
Defensive priority
Medium priority due to potential for incorrect access or filtering decisions.
Recommended defensive actions
- Inventory and assess systems using Perl versions from 5.9.4 before 5.41.9
- Apply vendor remediation when available
- Monitor for potential incorrect access or filtering decisions
- Implement compensating controls to mitigate potential risks
- Review system configurations and logs for signs of exploitation
- Conduct a thorough risk assessment to identify potential vulnerabilities
- Develop a plan for applying vendor remediation and verifying its effectiveness
Evidence notes
The CVE record and NVD entry provide details on the vulnerability. However, further analysis is needed to fully understand the impact and affected systems. Affected systems likely include those using Perl versions from 5.9.4 before 5.41.9. Defenders should verify system configurations, review logs for potential incorrect access or filtering decisions, and assess the vulnerability's impact on their specific environments. Additional analysis is required to determine the full scope of affected systems and potential mitigations.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-19487 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-19487
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-19487 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-19487
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/Perl/perl5/commit/1a21abacaf6f684928bae8baaa153733c8c238eb.patch
9b29abf9-4ab0-4765-b253-1875cd9b441e
-
Source reference
Unverified legacy reference
URL: https://github.com/Perl/perl5/issues/22892
9b29abf9-4ab0-4765-b253-1875cd9b441e
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.