Skip to main content
VulnerabilityPublished Updated

CVE-2026-41205: sqlalchemy mako · Path Traversal

Affects sqlalchemy makoSource CVE Database V5

0
Compare

Public exploit available · CVSS 7.7 High : upgrade to 1.3.11 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.11
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade sqlalchemy mako to 1.3.11.

Affected software

ProductAffectedFixed in
sqlalchemymakoAffected
  • <1.3.11
Fixed in
  • 1.3.11
PyPImakopkg:pypi/makoOther threatsAffected
  • <1.3.11
Fixed in
  • 1.3.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Mako to version 1.3.11 or later, where this path traversal vulnerability is fixed. Avoid passing untrusted input directly to TemplateLookup.get_template() as an additional precaution. Patch status is confirmed by the vendor stating the issue is fixed in 1.3.11.

Description

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.

References

Community reviews

Loading reviews…