# CVE-2025-7346: pyLoad is vulnerable to attacks that bypass localhost restrictions, enabling the creation of arbitrary packages

> Unauthenticated attackers can bypass localhost restrictions to create arbitrary packages, potentially leading to privilege escalation or code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-x698-5hjm-w2m5, PYSEC-2026-1822

## What is CVE-2025-7346?

CVE-2025-7346 is a high-severity authentication bypass vulnerability in Pyload, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Any unauthenticated attacker can bypass the localhost 
restrictions posed by the application and utilize this to create 
arbitrary packages

Weakness: CWE-281 (Improper Preservation of Permissions)

## Which versions are affected by CVE-2025-7346?

3 open source packages ship an affected version, including pyload-ng.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyload-ng` | PyPI | All versions to 0.5.0b3.dev88 | None |
| `pyload-ng` | PyPI | All versions to 0.5.0b3.dev88 | None |
| `pyload-ng` | PyPI | All versions to 0.5.0b3.dev88 | None |

## How do I fix CVE-2025-7346?

No fix has been published for CVE-2025-7346 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-7346 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7346 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7346 and fix it if it is affected.

What it is: CVE-2025-7346 is a high-severity authentication bypass vulnerability in Pyload, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7346 exists.

Affected packages and fixed versions:
- pyload-ng (PyPI): affected all versions up to 0.5.0b3.dev88; no fix listed
- pyload-ng (PyPI): affected all versions up to 0.5.0b3.dev88; no fix listed
- pyload-ng (PyPI): affected all versions up to 0.5.0b3.dev88; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7346/ (Markdown: https://insights.sbomify.com/CVE-2025-7346/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7346
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7346
- OSV: https://osv.dev/vulnerability/CVE-2025-7346

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7346/
Summaries are generated and may contain mistakes; the official description above is the record.