Skip to main content
VulnerabilityPublished

CVE-2026-116130: HTTP::Parser::XS versions before 0.18 for Perl truncate PATH_INFO at an encoded NUL byte in

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116130· High

Not known to be exploited : upgrade to 0.18 soon.

Data as of 30 Oct 2026, 17:04 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 0.18

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 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 30 Oct 2026.

What to do

Upgrade HTTP-Parser-XS (Perl module) to 0.18.

Affected software

ProductAffectedFixed in
HTTP-Parser-XSAffected
  • <0.18
Fixed in
  • 0.18
CPANHTTP-Parser-XSpkg:cpan/HTTP-Parser-XSOther threatsAffected
  • <0.18
Fixed in
  • 0.18

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

AI-suggested

Users should upgrade to HTTP::Parser::XS version 0.18 or later once available to address this issue. Until then, consider using the pure-Perl backend which is not affected by this vulnerability. Monitor vendor advisories for official remediation guidance.

Description

HTTP::Parser::XS versions before 0.18 for Perl have a vulnerability where the PATH_INFO is truncated at an encoded NUL byte (%00) during HTTP request parsing. This occurs because the XS parser URL-decodes the request path and uses strlen() to measure it, causing the path to end prematurely at the first decoded NUL byte. The pure-Perl backend is not affected. This discrepancy can allow a remote attacker to send a path that a proxy or filter inspects fully, while the application routes on a truncated, shorter path.

References

Community reviews

Loading reviews…