# pyLoad: Server-Side Request Forgery via Download Link Submission Enables Cloud Metadata Exfiltration

Advisory record · `GHSA-m74m-f7cr-432x`

- **Identifiers:** `GHSA-m74m-f7cr-432x` · `CVE-2026-33992` · `PYSEC-2026-497`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 29 Jun 2026
- **Updated:** 1 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `pyload-ng` (PyPI): affected `<=0.5.0b3.dev96`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GHSA-m74m-f7cr-432x: pyLoad (PyPI package pyload-ng, versions up to and including 0.5.0b3.dev96) accepts arbitrary URLs when packages are added, without checking the destination. An authenticated user with any role can use this server-side request forgery to read internal services and cloud metadata, which the source says can expose instance credentials and SSH keys. No fixed version is listed; the source suggests restricting URL schemes and blocking private and metadata addresses.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.3 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0041, the 36th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 29 Jun 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-m74m-f7cr-432x](https://github.com/advisories/GHSA-m74m-f7cr-432x)
- [OSV: GHSA-m74m-f7cr-432x](https://osv.dev/vulnerability/GHSA-m74m-f7cr-432x)
- <https://github.com/pyload/pyload/security/advisories/GHSA-m74m-f7cr-432x>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33992>
- <https://github.com/pyload/pyload/commit/b76b6d4ee5e32d2118d26afdee1d0a9e57d4bfe8>
- <https://github.com/pyload/pyload>
- <https://pypi.org/project/pyload-ng>
- <https://github.com/advisories/GHSA-m74m-f7cr-432x>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m74m-f7cr-432x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m74m-f7cr-432x/>. Everything for agents: <https://agentprime.io/llms.txt>.