CVSS 4.0
2.3 lowCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:NCVE-2026-121967
Low (2.3).
Coder 2.28.0 before 2.29.22, 2.30.0 before 2.34.13, 2.35.0 before 2.35.10, 2.36.0 before 2.36.8, 2.37.0 before 2.37.5, and 2.38.0 before 2.38.1 contains a path traversal vulnerability in the AI Gateway passthrough router, which forwards percent-encoded dot segments upstream without rejecting them. Authenticated users can send paths such as %2e%2e or ..%2F under allowlisted prefixes to reach unintended provider endpoints using the deployment's centrally managed provider key.
Severity
CVSS 3.1
4.9 mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-121967 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121967?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121967?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-121967 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| coder | from 2.37.0 before 2.37.5 |
| coder | from 2.36.0 before 2.36.8 |
| coder | from 2.35.0 before 2.35.10 |
| coder | from 2.30.0 before 2.34.13 |
| coder | from 2.28.0 before 2.29.22 |
| coder | from 2.38.0 before 2.38.1 |
Attack patterns (CAPEC)
- CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
- CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
- CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
- CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
- CAPEC-126 Path Traversal Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.