VulnerabilityPublished 19 Sep 2026Updated 21 Sep 2026

CVE-2026-82560: podlators (Perl module) · Infinite Loop

Affects podlators (Perl module)Source CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 6.1.1 soon.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.1.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-qcgj-vx8w-rqfq

What to do

Upgrade podlators (Perl module) to 6.1.1.

Affected software

Product	Affected	Fixed in
CPANpodlators`pkg:cpan/podlators`Other threats	Affected <6.1.1	Fixed in 6.1.1
CPANperl`pkg:cpan/perl`Other threats	Affected <=5.45.2	Fixed in–

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

AI-suggested

A fix is available in Pod::Text version 6.1.1. Users should upgrade to version 6.1.1 or later to remediate this vulnerability. No vendor advisory content was provided, so check the official Pod::Text or Perl module repositories for the patch and upgrade instructions.

Description

CVE-2026-82560 is a high-severity vulnerability in Pod::Text for Perl versions before 6.1.1. It involves an infinite loop triggered by formatting a POD document with deeply nested =over directives that cause the margin to reach zero width. This results in CPU and memory exhaustion as the formatting process never returns and the output grows uncontrollably.

Impact

An attacker can supply a specially crafted POD document that triggers an infinite loop during formatting, causing the process to consume excessive CPU and memory resources until exhaustion. This results in a denial of service condition but does not impact confidentiality or integrity.

Summary

Pod::Text versions prior to 6.1.1 contain a loop with an unreachable exit condition (CWE-835) when processing POD documents with nested =over directives. Each =over increases the margin indent, which wrap() subtracts from the output width to determine available text space. When the available space reaches zero, the line-splitting substitution matches an empty string, causing the loop to consume no input but append margin padding repeatedly. This infinite loop leads to unbounded CPU and memory consumption, effectively causing a denial of service.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Oct 2026, 23:31 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats