CVE-2023-0435 json
Excessive Attack Surface in pyload/pyload
published 2023-01-22 3 y ago modified 2026-07-01 4 mo ago also GHSA-6jmx-pv77-wm5w , PYSEC-2026-494 , EUVD-2023-0366
- cvss
- 4.0
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
Excessive Attack Surface in GitHub repository pyload/pyload prior to 0.5.0b3.dev41.
Patch / fix
- pypi pyload-ng 0.5.0b3.dev41
- pyload pyload/pyload 0.5.0b3.dev41
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 19 mo ago
Exploit prediction
0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/a3e32ad5-caee-4f43-b10a-4a876d4e3f1d referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 4.0 | CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pyload-ng | <0.5.0b3.dev41 |
0.5.0b3.dev41 |
Affected products
- pyload pyload/pyload
Classification
- Weakness
-
- CWE-1125 Excessive Attack Surface
References
-
github.com
/pyload/pyload/commit/431ea6f0371d748df66b344a05ca1a8e0310cff3
web, patch, third-party-advisory
-
huntr.dev
/bounties/a3e32ad5-caee-4f43-b10a-4a876d4e3f1d
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-0435
advisory
-
github.com
/pyload/pyload
package
-
pypi.org
/project/pyload-ng
package
-
github.com
/advisories/GHSA-6jmx-pv77-wm5w
advisory
Sources
- CVE List CVE-2023-0435
- GitHub Advisory GHSA-6jmx-pv77-wm5w
- NVD CVE-2023-0435
- OSV PYSEC-2026-494
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.