PatchSiren cyber security CVE debrief
CVE-2026-19873 HTML::FormFu CVE debrief
HTML::FormFu versions through 2.08 for Perl are vulnerable to resource exhaustion via an unbounded repeat count from the query string in Repeatable elements. This vulnerability can be exploited via a simple GET request, leading to memory and CPU exhaustion. Users should verify and apply vendor remediation if available, implement compensating controls, and monitor for potential exploitation attempts. The CVE record was published on 2026-08-31T10:16:49.790Z and has not been modified since then. Limited information is available; further verification is needed.
- Vendor
- HTML::FormFu
- Product
- HTML::FormFu
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-31
- Original CVE updated
- 2026-08-31
- Advisory published
- 2026-08-31
- Advisory updated
- 2026-08-31
Who should care
Users of HTML::FormFu versions through 2.08 for Perl should be concerned about this vulnerability, as it can be exploited via a simple GET request, and a single request can exhaust memory and CPU. Affected operators, platforms, and security teams should review and apply vendor guidance, implement compensating controls, and monitor for potential exploitation attempts.
Technical summary
HTML::FormFu versions through 2.08 for Perl allow resource exhaustion via an unbounded repeat count from the query string in Repeatable elements. When a Repeatable element has counter_name set, its process method reads the repeat count from the named query string parameter, checks only that it is a positive integer, and passes it to repeat, which deep-clones the element's child subtree once per iteration. This can lead to a large number of clones, causing memory and CPU exhaustion. The vulnerability can be exploited via a simple GET request.
Defensive priority
This vulnerability allows for resource exhaustion via an unbounded repeat count from the query string in Repeatable elements in HTML::FormFu versions through 2.08 for Perl. A single request can exhaust memory and CPU, making it a high-priority defensive concern.
Recommended defensive actions
- Verify and apply vendor remediation if available
- Implement compensating controls to limit exposure
- Monitor for and respond to potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The vulnerability is caused by the lack of a cap on the repeat count in Repeatable elements, which can lead to deep-cloning of the element's child subtree and exhaustion of memory and CPU. The latest release on CPAN is 2.07, from 2018, and version 2.08 exists only in the git repository. Limited information available; further verification needed.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-19873 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-19873
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-19873 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-19873
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/FormFu/HTML-FormFu/issues/71
9b29abf9-4ab0-4765-b253-1875cd9b441e
-
Source reference
Unverified legacy reference
URL: https://security.metacpan.org/patches/H/HTML-FormFu/2.08/CVE-2026-19873-r1.patch
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.