CVE-2023-0297

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 96% (99th 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
Weaponized
9.8EG
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).
  • High exploitation likelihood — EPSS 96%
  • Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 96%CVSS: 9.8Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

Code Injection in GitHub repository pyload/pyload prior to 0.5.0b3.dev31.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
97
EG Risk 97/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation96% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (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 yes (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
96%
EPSS %ILE
99th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
96% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-23). 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: 3 days if the affected system is publicly exposed; 60 days 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 yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

January 14, 2023

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Oct 10, 2026
Patch available. Sources: github_commit.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.dev/bounties/3fd606f7-83e1-4265-b083-2e1889a05e65
GitHub commit

commit 7d73ba7919e5 (pyload/pyload)

Fix landed in pyload/pyload commit 7d73ba7919e5 — awaiting tagged release

https://github.com/pyload/pyload/commit/7d73ba7919e594d783b3411d7ddb87885aea782d

Affected Packages

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 20× 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.

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. 11 repeat rows among the latest 74 are merged into the row they repeat.

  1. 2026-10-24 00:59 UTCEG score recompute
  2. 2026-10-23 01:16 UTCEG score recompute
  3. 2026-10-22 01:32 UTCEG score recompute
  4. 2026-10-21 16:29 UTCEPSS rescoreEPSS 96% · 99th percentile
  5. 2026-10-21 01:50 UTCEG score recompute
  6. 2026-10-20 02:06 UTCEG score recompute
  7. 2026-10-19 01:18 UTCEG score recompute
  8. 2026-10-18 08:18 UTCEG score recompute
  9. 2026-10-18 01:33 UTCEG score recompute
  10. 2026-10-17 01:49 UTCEG score recompute
  11. 2026-10-16 02:03 UTCEG score recompute
  12. 2026-10-14 21:49 UTCEG score recompute
  13. 2026-10-14 16:29 UTCEPSS rescoreEPSS 96% · 99th percentile
  14. 2026-10-13 17:38 UTCEG score recompute
  15. 2026-10-12 17:46 UTCEG score recompute
  16. 2026-10-11 22:03 UTCEG score recompute
  17. 2026-10-05 17:40 UTCEPSS rescoreEPSS 96% · 99th percentile
  18. 2026-09-30 16:13 UTCEG score recompute
  19. 2026-09-26 15:55 UTCEPSS rescoreEPSS 96% · 99th percentile
  20. 2026-09-24 14:00 UTCEPSS rescoreEPSS 96% · 99th percentile
  21. 2026-09-23 23:11 UTCOSV refresh
  22. 2026-09-11 14:50 UTCEPSS rescoreEPSS 96% · 99th percentile
  23. 2026-09-07 15:59 UTCEPSS rescoreEPSS 96% · 99th percentile
  24. 2026-09-06 13:45 UTCEPSS rescoreEPSS 96% · 99th percentile
  25. 2026-09-05 15:25 UTCEPSS rescoreEPSS 96% · 99th percentile
Show 38 more
  1. 2026-09-04 17:54 UTCOSV refresh
  2. 2026-08-30 19:15 UTCEPSS rescoreEPSS 96% · 99th percentile
  3. 2026-08-28 21:38 UTCEPSS rescoreEPSS 96% · 99th percentile
  4. 2026-08-27 14:22 UTCEPSS rescoreEPSS 96% · 99th percentile
  5. 2026-08-25 13:46 UTCEPSS rescoreEPSS 96% · 99th percentile
  6. 2026-08-18 05:04 UTCOSV refresh
  7. 2026-08-16 14:53 UTCEPSS rescoreEPSS 96% · 99th percentile
  8. 2026-08-13 21:58 UTCEPSS rescoreEPSS 96% · 99th percentile
  9. 2026-08-08 16:34 UTCEPSS rescoreEPSS 96% · 99th percentile
  10. 2026-08-02 23:57 UTCOSV refresh
  11. 2026-08-01 04:13 UTCEPSS rescoreEPSS 96% · 99th percentile
  12. 2026-07-30 16:25 UTCEPSS rescoreEPSS 96% · 99th percentile
  13. 2026-07-30 01:28 UTCEPSS rescoreEPSS 96% · 99th percentile
  14. 2026-07-26 14:52 UTCEPSS rescoreEPSS 96% · 99th percentile
  15. 2026-07-24 14:15 UTCEPSS rescoreEPSS 96% · 99th percentile
  16. 2026-07-23 02:17 UTCEG score recompute
  17. 2026-07-22 23:04 UTCEG score recompute
  18. 2026-07-20 17:05 UTCEPSS rescoreEPSS 96% · 99th percentile
  19. 2026-07-16 08:49 UTCOSV refresh
  20. 2026-07-08 15:13 UTCEPSS rescoreEPSS 96% · 99th percentile
  21. 2026-07-06 16:25 UTCEPSS rescoreEPSS 97% · 99th percentile
  22. 2026-07-05 02:28 UTCEPSS rescoreEPSS 97% · 99th percentile
  23. 2026-06-30 23:20 UTCEPSS rescoreEPSS 97% · 99th percentile
  24. 2026-06-28 08:21 UTCOSV refresh
  25. 2026-06-27 03:07 UTCEPSS rescoreEPSS 97% · 99th percentile
  26. 2026-06-23 21:31 UTCEPSS rescoreEPSS 97% · 99th percentile
  27. 2026-06-16 17:51 UTCEPSS rescoreEPSS 97% · 99th percentile
  28. 2026-06-15 17:47 UTCEPSS rescoreEPSS 97% · 99th percentile
  29. 2026-06-13 22:59 UTCEPSS rescoreEPSS 93% · 99th percentile
  30. 2026-06-11 13:58 UTCEPSS rescoreEPSS 93% · 99th percentile
  31. 2026-06-10 18:47 UTCOSV refresh
  32. 2026-06-08 14:15 UTCEPSS rescoreEPSS 93% · 99th percentile
  33. 2026-06-07 15:23 UTCEPSS rescoreEPSS 93% · 99th percentile
  34. 2026-06-06 13:46 UTCEPSS rescoreEPSS 93% · 99th percentile
  35. 2026-06-05 22:46 UTCEPSS rescoreEPSS 93% · 99th percentile
  36. 2026-05-29 13:43 UTCEPSS rescoreEPSS 93% · 99th percentile
  37. 2026-05-25 08:37 UTCEG score recompute
  38. 2026-05-24 17:12 UTCOSV refresh

Publicly available exploits

(5 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 2 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-51532✓ verified
    Published Jun 14, 2023

    PyLoad 0.5.0 - Pre-auth Remote Code Execution (RCE)

    Open source ↗
  • Metasploitexploit/linux/http/pyload_js2py_exec✓ verified
    Published Feb 21, 2023

    pyLoad js2py Python Execution

    Open source ↗
  • Nucleihttp/cves/2023/CVE-2023-0297.yaml
    Published Jul 7, 2023

    PyLoad 0.5.0 - Pre-auth Remote Code Execution (RCE)

    Open source ↗
  • GitHub PoCSmall-ears/CVE-2023-0297
    Published Feb 15, 2023

    poc

    Open source ↗
  • GitHub PoCbAuh0lz/CVE-2023-0297_Pre-auth_RCE_in_pyLoad
    Published Jan 9, 2023

    CVE-2023-0297: The Story of Finding Pre-auth RCE in pyLoad

    Open source ↗

Frequently asked(5)

What is CVE-2023-0297?
CVE-2023-0297 is a critical-severity vulnerability; its CVE record was published on January 14, 2023. Code Injection in GitHub repository pyload/pyload prior to 0.5.0b3.dev31.
When was the CVE record for CVE-2023-0297 published?
The CVE record for CVE-2023-0297 was published on January 14, 2023. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-0297 actively exploited?
CVE-2023-0297 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified, and CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 96% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-0297?
CVE-2023-0297 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-0297?
A fix for CVE-2023-0297 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-0297

Explore →

Is Your Infrastructure Affected by CVE-2023-0297?

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