CVE-2026-61536

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). 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, secondary
Elevated
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.5%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

The CVE record names the fixed release — apply it.

Banks generates meaningful LLM prompts using a simple template language. In versions prior to 2.4.3, banks parses Tool JSON objects from the rendered body of {% completion %} blocks and later resolves their import_path field through importlib.import_module(...) + getattr(...) to obtain the callable that handles a tool call. There is no allowlist or sanitization on import_path, so any importable Python attribute (e.g. os.system, subprocess.getoutput) can be selected. When the LLM emits a tool_calls entry whose function.name matches the attacker-supplied tool name, the resolved callable is invoked with kwargs decoded from tool_call.function.arguments, yielding arbitrary code execution in the banks-hosting process. This is distinct from GHSA-gphh-9q3h-jgpp / CVE-2026-44209. That advisory was fixed in 2.4.2 by switching src/banks/env.py from Environment to SandboxedEnvironment. The fix does not touch src/banks/extensions/completion.py, and the unsafe import + getattr chain still executes on 2.4.2. The malicious Tool JSON is plain text in the rendered template body — it requires no Jinja attribute access, so the sandbox is irrelevant. This issue has been fixed in version 2.4.3.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
50
EG Risk 50/100CISA SSVC

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%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 30, 2026

Last Modified

July 31, 2026

Advisory Details (1)

Auto-updated Jul 30, 2026
🔬 Proof of concept available. Fix named in the CVE record. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

Unsafe importlib.import_module of attacker-controlled Tool.import_path in CompletionExtension allows RCE · Advisory · masci/banks · GitHub

Affected: 2.4.2 by switching

https://github.com/masci/banks/security/advisories/GHSA-64vx-6h2c-rjh7

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 42× 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 116 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61536?
CVE-2026-61536 is a high vulnerability published on July 30, 2026. Banks generates meaningful LLM prompts using a simple template language. In versions prior to 2.4.3, banks parses Tool JSON objects from the rendered body of {% completion %} blocks and later resolves their importpath field through importlib.importmodule(...) + getattr(...) to obtain the callable…
When was CVE-2026-61536 disclosed?
CVE-2026-61536 was first published on July 30, 2026, with the most recent update on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61536 actively exploited?
CVE-2026-61536 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61536?
CVE-2026-61536 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61536?
The CVE record for CVE-2026-61536 names the fix: "This issue has been fixed in version 2.4.3."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61536

Explore →

Is Your Infrastructure Affected by CVE-2026-61536?

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

Book a Demo →Browse All CVEs