VulnerabilityPublished 11 May 2026

CVE-2026-44226: pyload · Generation of Error Message Containing Sensitive Information

Affects pyloadSource GCVE Database

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.5.0b3.dev100 when convenient.

Data as of 27 Oct 2026, 00:27 UTC

CVSS 3.1 base score

5.3Medium

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

Patch: Available – fixed in 0.5.0b3.dev100

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

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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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.

What to do

Upgrade pyload to 0.5.0b3.dev100.

Affected software

Product	Affected	Fixed in
pyload pyload	Affected <0.5.0b3.dev100	Fixed in 0.5.0b3.dev100

AI-suggested

Upgrade pyLoad to version 0.5.0b3.dev100 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by preventing detailed error tracebacks from being exposed to unauthenticated users.

Description

pyLoad versions prior to 0.5.0b3.dev100 have a vulnerability where the web interface returns full Python traceback details to unauthenticated users when an unhandled exception occurs. This happens because the /web/<path:filename> endpoint is accessible without authentication and processes attacker-controlled template names, allowing an attacker to trigger server exceptions and obtain internal stack traces. This issue is fixed in version 0.5.0b3.dev100.

Impact

An unauthenticated attacker can obtain internal Python traceback details by triggering exceptions via the web interface. This information disclosure can aid attackers in understanding the internal workings of the application, potentially facilitating further attacks. The CVSS 3.1 base score is 5.3 (medium severity), reflecting the network attack vector, low complexity, no privileges or user interaction required, and limited confidentiality impact.

Summary

pyLoad, an open-source Python download manager, has a CWE-209 vulnerability in versions before 0.5.0b3.dev100. The pyload-ng WebUI endpoint /web/<path:filename> is accessible without authentication and renders templates based on user input. An unauthenticated attacker can request a non-existent template to trigger an unhandled exception, causing the server to return detailed Python traceback information in the HTTP response. This leakage of internal error messages may expose sensitive information about the server environment. The vulnerability is addressed in version 0.5.0b3.dev100.

CWE-209Generation of Error Message Containing Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
Implementation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Implementation · Attack Surface Reduction
Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
Padding Oracle Crypto Attack (opens in a new tab)
Query System for Information (opens in a new tab)
Blind SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/pyload/pyload/security/advisories/GHSA-c3gc-9pf2-84gg (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 00:27 UTC

WeaknessesCWE-209

Technical details

References

Community reviews

Related threats