CVE-2026-41205

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% 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

A fix is available — apply it.

Mako is a template library written in Python. Prior to 1.3.11, TemplateLookup.get_template() is vulnerable to path traversal when a URI starts with // (e.g., //../../../secret.txt). The root cause is an inconsistency between two slash-stripping implementations. Any file readable by the process can be returned as rendered template content when an application passes untrusted input directly to TemplateLookup.get_template(). This vulnerability is fixed in 1.3.11.

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
29%
KEV
Not listed

Published

April 23, 2026

Last Modified

May 20, 2026

Advisory Details (3)

Auto-updated May 20, 2026
Patch available. Sources: github.
github Patch Available

Path traversal via double-slash URI prefix in TemplateLookup · Advisory · sqlalchemy/mako · GitHub

https://github.com/sqlalchemy/mako/security/advisories/GHSA-v92g-xgxw-vvmm
generic

Release 1.3.11 · sqlalchemy/mako · GitHub

https://github.com/sqlalchemy/mako/releases/tag/rel_1_3_11
generic

Fix path traversal via double-slash URI prefix in TemplateLookup · sqlalchemy/mako@e05ac61 · GitHub

https://github.com/sqlalchemy/mako/commit/e05ac61989a7fb9dd7dcde6cfd72dc48328719a3

Vendor Advisories for CVE-2026-41205(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-mako (1.3.2-1ubuntu0.1) @ noble2026-06-15ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
mako1.1.3+ds1-2 ... 1.3.9-1 (17 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
mako1.2.4+ds-1 ... 1.3.9-1 (13 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
mako1.3.10-1, 1.3.10-2, 1.3.10-3, 1.3.9-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
mako1.3.10-1, 1.3.10-2, 1.3.10-3, 1.3.9-1——
PyPI(1)
PackageVulnerable rangeFixed inDependents
mako0.1.0 ... 1.3.9 (77 versions)1.3.11—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 58× 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 175 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41205?
CVE-2026-41205 is a high vulnerability published on April 23, 2026. Mako is a template library written in Python. Prior to 1.3.11, TemplateLookup.gettemplate() is vulnerable to path traversal when a URI starts with // (e.g., //../../../secret.txt). The root cause is an inconsistency between two slash-stripping implementations. Any file readable by the process can…
When was CVE-2026-41205 disclosed?
CVE-2026-41205 was first published in the National Vulnerability Database on April 23, 2026, with the most recent update on May 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41205 actively exploited?
CVE-2026-41205 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 71.1% of all scored CVEs.
What is the CVSS score of CVE-2026-41205?
CVE-2026-41205 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-41205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41205, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41205?

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

Start Free Scan →Browse All CVEs