CVE-2026-42313

HIGHNVD 8.38.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.3 under NVD CVSS v3. EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-29121 (ENISA EUVD) · GHSA-pg67-9wjv-mr85 (GitHub Security Advisories)Source: ENISA EUVD

8.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev100, the set_config_value() API method (@permission(Perms.SETTINGS)) in src/pyload/core/api/__init__.py gates security-sensitive options behind a hand-maintained allowlist ADMIN_ONLY_CORE_OPTIONS. The allowlist contains ("proxy", "username") and ("proxy", "password") — which protect the proxy credentials — but it does not include ("proxy", "enabled"), ("proxy", "host"), ("proxy", "port"), or ("proxy", "type"). Any authenticated user with the non-admin SETTINGS permission can enable proxying and point pyload at any host they control. From that point, every outbound download, captcha fetch, update check, and plugin HTTP call is transparently routed through the attacker. This is a direct continuation of the fix family CVE-2026-33509 / CVE-2026-35463 / CVE-2026-35464 / CVE-2026-35586, each of which patched a different missed option in the same allowlist. This vulnerability is fixed in 0.5.0b3.dev100.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
53
EG Risk 53/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity83% × 45%
Impact severity (EG Severity): CVSS 8.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.3): severity, escalated by confirmed exploitation. This CVE's 8.3 is its impact severity (EG Severity), not escalated.

EG Severity
8.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 11, 2026

Last Modified

May 15, 2026

Advisory Details (1)

Auto-updated May 11, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

pyload-ng: non-admin SETTINGS users can redirect all outbound traffic through an attacker-controlled proxy via unrestricted `proxy.*` config (incomplete fix for CVE-2026-33509 / -35463 / -35464 / -35586) · Advisory · pyload/pyload · GitHub

https://github.com/pyload/pyload/security/advisories/GHSA-pg67-9wjv-mr85

Vendor Advisories for CVE-2026-42313(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pyload-ng0.5.0a5.dev528 ... 0.5.0b3.dev99 (104 versions)
  • every version up to 0.5.0b3.dev100: fixed in 0.5.0b3.dev100
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 191 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-25 14:29 UTCEG score recompute
  7. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-24 02:20 UTCEG score recompute
  9. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-18 03:41 UTCEG score recompute
  16. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-17 14:28 UTCEG score recompute
  18. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-12 16:07 UTCEG score recompute
  24. 2026-10-11 19:49 UTCEG score recompute
  25. 2026-10-11 17:03 UTCEG score recompute
Show 75 more
  1. 2026-10-11 14:29 UTCEG score recompute
  2. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  26. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  27. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  28. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  29. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  30. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  31. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  32. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  33. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  34. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  35. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  36. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  37. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  38. 2026-08-23 18:38 UTCEG score recompute
  39. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  40. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  41. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  42. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  43. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  44. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  45. 2026-08-17 11:10 UTCEG score recompute
  46. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  47. 2026-08-16 04:25 UTCEG score recompute
  48. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  49. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  50. 2026-08-14 02:58 UTCEG score recompute
  51. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  52. 2026-08-12 16:30 UTCEG score recompute
  53. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  54. 2026-08-11 15:47 UTCEG score recompute
  55. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  56. 2026-08-11 01:10 UTCEG score recompute
  57. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  58. 2026-08-10 00:30 UTCEG score recompute
  59. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  60. 2026-08-09 02:15 UTCEG score recompute
  61. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  62. 2026-08-07 19:18 UTCEG score recompute
  63. 2026-08-06 20:13 UTCEG score recompute
  64. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  65. 2026-08-05 21:57 UTCEG score recompute
  66. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  67. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  68. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  69. 2026-08-03 19:26 UTCEG score recompute
  70. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  71. 2026-08-02 13:13 UTCEG score recompute
  72. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  73. 2026-08-02 02:05 UTCEG score recompute
  74. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  75. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-42313?
CVE-2026-42313 is a high-severity vulnerability; its CVE record was published on May 11, 2026. pyLoad is a free and open-source download manager written in Python. Prior to 0.5.0b3.dev100, the setconfigvalue() API method (@permission(Perms.SETTINGS)) in src/pyload/core/api/init.py gates security-sensitive options behind a hand-maintained allowlist ADMINONLYCORE_OPTIONS. The allowlist…
When was the CVE record for CVE-2026-42313 published?
The CVE record for CVE-2026-42313 was published on May 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 15, 2026; the record at its source may have been updated since.
Is CVE-2026-42313 actively exploited?
CVE-2026-42313 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42313?
CVE-2026-42313 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-42313?
A fix for CVE-2026-42313 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42313 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42313

Explore →

Is Your Infrastructure Affected by CVE-2026-42313?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs