PPTAgent: Arbitrary File Write via save_generated_slides
CVE-2026-42080GHSA-pxhg-7xr2-w7xg
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (pptagent 1.1.36), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI pptagent
- Affected
- < 1.1.36
- Fixed in
- 1.1.36
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-pxhg-7xr2-w7xg lists affected ranges: PyPI pptagent >=0 <1.1.36 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-pxhg-7xr2-w7xg lists affected ranges: PyPI pptagent >=0 <1.1.36
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L
- EPSS
- CVE-2026-42080: 0.20% estimated exploitation activity in the next 30 days; percentile 9.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary This vulnerability has been fixed in https://github.com/icip-cas/PPTAgent/commit/418491a9a1c02d9d93194b5973bb58df35cf9d00. The savegeneratedslides MCP tool accepts a pptxpath argument and writes the generated PPTX file to that path without any workspace restriction or path validation: The call to pptx.parent.mkdir(parents=True, existok=True) creates any intermediate directories, and self.emptyprs.save(pptxpath) writes a valid PPTX binary (ZIP archive) to the specified path. No isrelativeto(workspace) check is performed — contrast with downloadfile in deeppresenter/tools/search.py:290, which correctly enforces workspace confinement. The server changes directory to WORKSPACE (if set) on startup, so relative paths land in the workspace. Absolute paths, however, reach any filesystem location accessible to the server process. Impact The concrete attack scenarios include 1. Cron persistence (root-running server): pptxpath = "/etc/cron.d/backdoor" → writes a PPTX ZIP to a path the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-pxhg-7xr2-w7xg
- Revision 1 · created ·
Published from osv record GHSA-pxhg-7xr2-w7xg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-42080 Advisory: PPTAgent: Arbitrary File Write via `save_generated_slides` IDs: CVE-2026-42080, GHSA-pxhg-7xr2-w7xg Record: https://patchnext.com/advisories/cve-2026-42080 (revision 2, source checked 26 Oct 2026, 13:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: pptagent 1.1.36. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI pptagent: affected < 1.1.36; fixed in 1.1.36 ## Suggested inspection (read-only) - `python -m pip show pptagent`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on pptagent. - 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-pxhg-7xr2-w7xg (OSV record GHSA-pxhg-7xr2-w7xg lists affected ranges: PyPI pptagent >=0 <1.1.36 (fixed)) - Verified: https://github.com/advisories/GHSA-pxhg-7xr2-w7xg (GitHub-reviewed advisory GHSA-pxhg-7xr2-w7xg lists affected ranges: PyPI pptagent >=0 <1.1.36) Commands are suggestions: review each one before running it.
Loading voting…