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.
CVE-2026-41205
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 74% 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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 28.2%
- KEV
- Not listed
Published
April 23, 2026
Last Modified
May 20, 2026
Advisory Details (3)
Auto-updated May 20, 2026Path traversal via double-slash URI prefix in TemplateLookup · Advisory · sqlalchemy/mako · GitHub
https://github.com/sqlalchemy/mako/security/advisories/GHSA-v92g-xgxw-vvmmRelease 1.3.11 · sqlalchemy/mako · GitHub
https://github.com/sqlalchemy/mako/releases/tag/rel_1_3_11Fix path traversal via double-slash URI prefix in TemplateLookup · sqlalchemy/mako@e05ac61 · GitHub
https://github.com/sqlalchemy/mako/commit/e05ac61989a7fb9dd7dcde6cfd72dc48328719a3Vendor 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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | python3-mako (1.3.2-1ubuntu0.1) @ noble | 2026-06-15 | ubuntu |
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
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| mako | 0.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 9× in last 7d / 39× 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 118 total refreshes for this CVE.
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 02:25 UTCEG score recompute
- 2026-06-15 02:25 UTCVendor advisory
- 2026-06-14 12:18 UTCEG score recompute
- 2026-06-14 12:18 UTCVendor advisory
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 03:23 UTCEG score recompute
- 2026-06-11 14:24 UTCEG score recompute
- 2026-06-11 14:24 UTCVendor advisory
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 18:19 UTCEG score recompute
- 2026-06-10 18:19 UTCVendor advisory
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 05:21 UTCEG score recompute
- 2026-06-10 05:21 UTCVendor advisory
- 2026-06-09 16:21 UTCEG score recompute
- 2026-06-09 16:21 UTCVendor advisory
- 2026-06-09 03:24 UTCEG score recompute
- 2026-06-09 03:24 UTCVendor advisory
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 09:18 UTCEG score recompute
- 2026-06-08 09:18 UTCVendor advisory
- 2026-06-07 20:20 UTCEG score recompute
- 2026-06-07 20:20 UTCVendor advisory
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 07:22 UTCEG score recompute
- 2026-06-07 07:22 UTCVendor advisory
- 2026-06-06 18:24 UTCEG score recompute
- 2026-06-06 18:24 UTCVendor advisory
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 05:25 UTCEG score recompute
- 2026-06-06 05:25 UTCVendor advisory
- 2026-06-05 22:47 UTCEPSS rescore
- 2026-06-05 16:25 UTCEG score recompute
- 2026-06-05 16:25 UTCVendor advisory
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 03:06 UTCEG score recompute
- 2026-06-05 03:06 UTCVendor advisory
- 2026-06-04 14:08 UTCEG score recompute
- 2026-06-04 14:08 UTCVendor advisory
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 01:09 UTCEG score recompute
- 2026-06-04 01:09 UTCVendor advisory
- 2026-06-03 12:11 UTCEG score recompute
- 2026-06-03 12:11 UTCVendor advisory
- 2026-06-02 20:13 UTCEPSS rescore
- 2026-06-02 16:16 UTCEG score recompute
- 2026-06-02 16:16 UTCVendor advisory
- 2026-06-02 03:18 UTCEG score recompute
- 2026-06-02 03:18 UTCVendor advisory
- 2026-06-01 14:18 UTCEG score recompute
- 2026-06-01 14:18 UTCVendor advisory
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 13:51 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu · msrc
Frequently asked(5)
What is CVE-2026-41205?
When was CVE-2026-41205 disclosed?
Is CVE-2026-41205 actively exploited?
What is the CVSS score of CVE-2026-41205?
How do I remediate CVE-2026-41205?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41205
Is Your Infrastructure Affected by CVE-2026-41205?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.