Skip to content
Noroxi
OSV ecosystem advisory

GHSA-q9m2-fhv9-3jcf: `potato-annotation` has a Project-Boundary Bypass

MediumCVSS 5.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 20/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: potato-annotation (PyPI) 2.4.5.

Low priority for now. Upgrade to potato-annotation (PyPI) 2.4.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

## Summary `validate_path_security` 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/potato_proj_demo_evil/...` vs `/tmp/potato_proj_demo`) to be accepted. ## Details ### Affected source location (root cause) **File:** `potato/server_utils/config_module.py` **Snippet (lines 370–373):** ```python real_path = os.path.realpath(normalized_path) real_base = os.path.realpath(base_dir) if not real_path.startswith(real_base): raise ConfigSecurityError(...) ``` **Snippet (lines 384–389):** ```python real_path = os.path.realpath(normalized_path) check_dir = project_dir if project_dir else base_dir real_check_dir = os.path.realpath(check_dir) if not real_path.startswith(real_check_dir): raise ConfigSecurityError(...) ``` `startswith()` is string-based, so `/tmp/potato_proj_demo_evil/...` passes when checked against `/tmp/potato_proj_demo`. ### Confirmed affected call sites **File:** `potato/server_utils/config_module.py` 1) `validate_file_paths` task_dir branch (line 2113) ```python validated_task_dir = validate_path_security(task_dir, project_dir) ``` 2) `validate_file_paths` data_files branch (line 2151) ```python validated_path = validate_path_security(file_path, base_dir, project_dir) ``` 3) `validate_training_config` training.data_file branch (line 2286) ```python validated_path = validate_path_security(data_file, base_dir, project_dir) ``` ## PoC ```python from potato.server_utils.config_module import validate_path_security base = '/tmp/potato_proj_demo' vuln = '/tmp/potato_proj_demo_evil/file.txt' try: print('inside=', validate_path_security('/tmp/potato_proj_demo/file.txt', base, base)) except Exception as e: print('inside_error=', type(e).__name__, e) try: validate_path_security('/tmp/other_demo/file.txt', base, base) except Exception as e: print('baseline=', type(e).__name__, e) print('trigger=', validate_path_security(vuln, base, base)) ``` ## Impact - Can allow unauthorized sibling-prefix file access outside intended project boundary. - Can affect read paths (`data_files`, `training.data_file`, `base_css`, `header_logo`) and output/path placement depending on configuration.

Published
May 8, 2026
Updated
May 8, 2026
EPSS
—

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
20 / 40 · 5.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-q9m2-fhv9-3jcf

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
PyPIpotato-annotation

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPIpotato-annotationfrom 2.0.0 · before 2.4.52.4.5

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
PyPI:potato-annotation2.4.5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

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

osv

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records