CVE-2026-62663

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
7.5EG
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.5%CVSS: 7.5Exploit: No code on recordExposed 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.4, all four media filters (image, audio, video, document) in banks accept untrusted user input as file paths via Path(value) and pass them directly to open(file_path, "rb") without any path sanitization, canonicalization, or directory restriction. An attacker who controls template variables passed to a banks Prompt can use path traversal (../) to read arbitrary files accessible to the Python process—including .env files, SSH keys, cloud credentials, source code, /etc/passwd, and /etc/shadow—with the content returned base64-encoded in the rendered prompt output, making exfiltration trivial. This is particularly dangerous for applications that use banks to process user-provided template variables before sending prompts to an LLM. This issue has been fixed in version 2.4.4.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: 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

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

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

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 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 or medium mission impact; Attend at high (mission-essential systems).

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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

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

July 30, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 30, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Arbitrary File Read via Path Traversal in Media Filters (image/audio/video/document) · Advisory · masci/banks · GitHub

https://github.com/masci/banks/security/advisories/GHSA-98rr-gvc9-3cjh

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 132 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 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62663?
CVE-2026-62663 is a high-severity vulnerability; its CVE record was published on July 30, 2026. Banks generates meaningful LLM prompts using a simple template language. In versions prior to 2.4.4, all four media filters (image, audio, video, document) in banks accept untrusted user input as file paths via Path(value) and pass them directly to open(file_path, "rb") without any path…
When was the CVE record for CVE-2026-62663 published?
The CVE record for CVE-2026-62663 was published on July 30, 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 July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-62663 actively exploited?
CVE-2026-62663 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-62663?
CVE-2026-62663 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-62663?
The CVE record for CVE-2026-62663 names the fix: "This issue has been fixed in version 2.4.4."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62663?

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

Book a Demo →Browse All CVEs