Pyload log Injection via API /json/add_package in add_name parameter

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary A log injection vulnerability was identified in pyload in API /json/addpackage. This vulnerability allows user with add packages permission to inject arbitrary messages into the logs gathered by pyload. Details pyload will generate a log entry when creating new package using API /json/addpackage. This entry will be in the form of Added package 'NAMEOFPACKAGE' containing 'NUMBEROFLINKS' links. However, when supplied with the name of new package containing a newline, this newline is not properly escaped. Newlines are also the delimiter between log entries. This allows the attacker to inject new log entries into the log file. PoC Run pyload in the default configuration by running the following command We can now sign in as the pyload user who at least have add packages permissions. In my example, I will use the admin account to demonstrate this vulnerability. Now as an admin user, view the logs at http://localhost:8000/logs <img width="1918" height="912" alt="image"…

Published by the source

30 Jul 2025, 13:18 UTC

Last modified by the source

30 Jul 2025, 14:23 UTC

Source last checked

26 Oct 2026, 13:32 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3wwm-hjv7-23r3

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3wwm-hjv7-23r3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-3wwm-hjv7-23r3

Advisory: Pyload log Injection via API /json/add_package in add_name parameter
IDs: GHSA-3wwm-hjv7-23r3
Record: https://patchnext.com/advisories/ghsa-3wwm-hjv7-23r3 (revision 2, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pyload-ng: affected <= 0.5.0b3.dev89

## Suggested inspection (read-only)
- `python -m pip show pyload-ng`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pyload-ng.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3wwm-hjv7-23r3 (OSV record GHSA-3wwm-hjv7-23r3 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev89)
- Verified: https://github.com/advisories/GHSA-3wwm-hjv7-23r3 (GitHub-reviewed advisory GHSA-3wwm-hjv7-23r3 lists affected ranges: PyPI pyload-ng >=0 <=0.5.0b3.dev89)

Commands are suggestions: review each one before running it.