Advisory record · GHSA-m74m-f7cr-432x

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

CVSS 9.3 CriticalCriticalEPSS 0.0041 · 36th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

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.

PackageEcosystemAffectedFixed in
pyload-ngPyPI<=0.5.0b3.dev96No fixed version yet
Identifiers
GHSA-m74m-f7cr-432x · CVE-2026-33992 · PYSEC-2026-497
Weakness (CWE)
CWE-918
Published
29 Jun 2026
Updated
1 Jul 2026

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

ScoreRatingCVSSVectorSource
9.3 Critical 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0041, the 36th percentile, on 13 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

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.