CVE-2023-37274

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Auto-GPT is an experimental open-source application showcasing the capabilities of the GPT-4 language model. When Auto-GPT is executed directly on the host system via the provided run.sh or run.bat files, custom Python code execution is sandboxed using a temporary dedicated docker container which should not have access to any files outside of the Auto-GPT workspace directory. Before v0.4.3, the execute_python_code command (introduced in v0.4.1) does not sanitize the basename arg before writing LLM-supplied code to a file with an LLM-supplied name. This allows for a path traversal attack that can overwrite any .py file outside the workspace directory by specifying a basename such as ../../../main.py. This can further be abused to achieve arbitrary code execution on the host running Auto-GPT by e.g. overwriting autogpt/main.py which will be executed outside of the docker environment meant to sandbox custom python code execution the next time Auto-GPT is started. The issue has been patched in version 0.4.3. As a workaround, the risk introduced by this vulnerability can be remediated by running Auto-GPT in a virtual machine, or another environment in which damage to files or corruption of the program is not a critical problem.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

July 13, 2023

Last Modified

February 24, 2026

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 149 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-37274?
CVE-2023-37274 is a high vulnerability published on July 13, 2023. Auto-GPT is an experimental open-source application showcasing the capabilities of the GPT-4 language model. When Auto-GPT is executed directly on the host system via the provided run.sh or run.bat files, custom Python code execution is sandboxed using a temporary dedicated docker container which…
When was CVE-2023-37274 disclosed?
CVE-2023-37274 was first published in the National Vulnerability Database on July 13, 2023, with the most recent update on February 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-37274 actively exploited?
CVE-2023-37274 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.1% of all scored CVEs.
What is the CVSS score of CVE-2023-37274?
CVE-2023-37274 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-37274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-37274, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-37274

Explore →

Is Your Infrastructure Affected by CVE-2023-37274?

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

Start Free Scan →Browse All CVEs