● High · CVSS 7.7

How to Fix CVE-2026-41205: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Q: Is CVE-2026-41205 being exploited in the wild?

As of 2026-05-25, CVE-2026-41205 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

Q: What is the CVSS score for CVE-2026-41205?

The CVSS base score is 7.7 (High).

Q: What version fixes this?

The vendor advisory names the patched build. See the References section.

Q: Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

By Sai Kiran Pandrala

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-30935: ImageMagick has a heap Buffer Over-Read in BilateralBlurImage — ImageMagick has a heap Buffer Over-Read in BilateralBlurImage
How to Fix CVE-2026-8426: Cross-Site Request Forgery in Concrete CMS — Cross-Site Request Forgery in Concrete CMS
How to Fix CVE-2026-29058: Os command injection in AVideo-Encoder , Os command injection in AVideo-Encoder
How to Fix CVE-2026-8093: Improper Restriction of Operations within the Bounds of a Memory Buffer in Firefox , Improper Restriction of Operations within the Bounds of a Memory Buffer in Firefox
How to Fix CVE-2026-3556: CWE-122: Heap-based Buffer Overflow in Hue Bridge , CWE-122: Heap-based Buffer Overflow in Hue Bridge

Last verified: 2026-05-25

CVE-2026-41205 is a cwe-22: improper limitation of a pathname to a restricted directory ('path traversal') in sqlalchemy mako. Fix it by upgrading to the patched build from the vendor advisory.

⚡ At a glance


Severity	CVSS 7.7 - High
Actively exploited?	Not currently in the CISA KEV catalog
Affected	mako < 1.3.11
Fixed in	See vendor advisory
Type (CWE)	CWE-22: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-41205?

CVE-2026-41205 is a cwe-22: improper limitation of a pathname to a restricted directory ('path traversal') flaw in sqlalchemy mako. It carries a CVSS base score of 7.7 (high). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: 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.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of mako matches a version listed in the Affected row above.

Check the running version against the Affected row above using the product's admin console or --version flag.

How to fix CVE-2026-41205

Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for mako.

Generic upgrade pattern

If the affected product is a Linux package, upgrade via the system package manager:


# Debian / Ubuntu
sudo apt-get update && sudo apt-get upgrade -y

# RHEL / Rocky / Alma
sudo dnf upgrade --security -y

If it ships as a Windows installer, download the patched build from the vendor advisory and:


# Vendor advisory: https://github.com/sqlalchemy/mako/security/advisories/GHSA-v92g-xgxw-vvmm
Start-Process msiexec.exe -ArgumentList '/i <patched-installer>.msi /qn /norestart' -Wait
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | \
    Where-Object DisplayName -match '<product-name>' | Select-Object DisplayName, DisplayVersion

After applying the patch

Restart the service or device so the patched binary loads.
Confirm the running version matches the Fixed in row using the verification command below.
Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.


# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4


# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

Check the running version against the Affected row above using the product's admin console or --version flag.

Expected: a version at or above the patched build named in the vendor advisory.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-41205 being exploited in the wild?