potato-annotation has a Project-Boundary Bypass

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary validatepathsecurity uses string-prefix containment (startswith) for boundary checks. This allows paths that are outside the intended project directory but share its prefix string (e.g., /tmp/potatoprojdemoevil/... vs /tmp/potatoprojdemo) to be accepted. Details Affected source location (root cause) File: potato/serverutils/configmodule.py Snippet (lines 370–373): Snippet (lines 384–389): startswith() is string-based, so /tmp/potatoprojdemoevil/... passes when checked against /tmp/potatoprojdemo. Confirmed affected call sites File: potato/serverutils/configmodule.py 1) validatefilepaths taskdir branch (line 2113) 2) validatefilepaths datafiles branch (line 2151) 3) validatetrainingconfig training.datafile branch (line 2286) PoC Impact - Can allow unauthorized sibling-prefix file access outside intended project boundary. - Can affect read paths (datafiles, training.datafile, basecss, headerlogo) and output/path placement depending on configuration.

Published by the source

8 May 2026, 17:31 UTC

Last modified by the source

8 May 2026, 17:49 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-q9m2-fhv9-3jcf

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-q9m2-fhv9-3jcf

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

# Patch Next advisory brief: GHSA-q9m2-fhv9-3jcf

Advisory: `potato-annotation` has a Project-Boundary Bypass
IDs: GHSA-q9m2-fhv9-3jcf
Record: https://patchnext.com/advisories/ghsa-q9m2-fhv9-3jcf (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: potato-annotation 2.4.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI potato-annotation: affected >= 2.0.0, < 2.4.5; fixed in 2.4.5

## Suggested inspection (read-only)
- `python -m pip show potato-annotation`: 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 potato-annotation.
- 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-q9m2-fhv9-3jcf (OSV record GHSA-q9m2-fhv9-3jcf lists affected ranges: PyPI potato-annotation >=2.0.0 <2.4.5 (fixed))
- Verified: https://github.com/advisories/GHSA-q9m2-fhv9-3jcf (GitHub-reviewed advisory GHSA-q9m2-fhv9-3jcf lists affected ranges: PyPI potato-annotation >=2.0.0 <2.4.5)

Commands are suggestions: review each one before running it.