Kan
CVE-2026-32255
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend unauthenticated request to /api/download/attachment
-
ExploitInject internal service URL in parameter
-
ExecutionServer fetches from internal network
-
ImpactReturn sensitive data to attacker
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Kan versions 0.5.4 and below with /api/download/attachment endpoint exposed. Remote unauthenticated attacker can exploit via HTTP GET request with arbitrary URL parameter. No user interaction required. Default installations vulnerable. |
| Impact | The CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) indicates this is a remotely exploitable vulnerability with low attack complexity, requiring no privileges or user interaction, with scope change and high confidentiality impact. The lack of authentication requirement makes this trivially exploitable by unauthenticated attackers. The ability to probe internal networks and extract sensitive data from cloud metadata endpoints (which often contain credentials, API keys, and configuration data) represents a critical real-world risk, particularly for cloud-hosted instances. A patch is available in version 0.5.5 as confirmed by the GitHub commit and release tag references, making this immediately actionable. Organizations running affected versions in cloud environments or with access to sensitive internal networks should prioritize remediation, as the combination of no authentication, network accessibility, and high confidentiality impact creates substantial risk for data exfiltration and lateral movement scenarios. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a GET request to https://target-kan-instance.com/api/download/attatchment?url=http://169.254.169.254/latest/meta-data/iam/security-credentials/ to retrieve AWS IAM credentials from the cloud metadata service. The Kan server fetches this internal URL and returns the credentials in the response body, which the attacker can then use to access the organization's AWS resources. The attacker could similarly target internal APIs, databases, or configuration management systems to extract sensitive data or map the internal network topology, all without requiring any authentication or user interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 18, 2026
Kan, an open-source project management tool, contains a Server-Side Request Forgery (SSRF) vulnerability in its unauthenticated /api/download/attatchment endpoint in versions 0.5.4 and below. Attackers can exploit this to make arbitrary HTTP requests from the server to internal services, cloud metadata endpoints (such as AWS EC2 metadata at 169.254.169.254), or private network resources without any authentication. With a CVSS score of 8.6 (High) reflecting network-based attack vector, low complexity, and no privileges required, this poses significant risk for confidentiality breaches in affected deployments.
RemediationAI
Upgrade Kan to version 0.5.5 or later, which contains the fix for this SSRF vulnerability as documented in the GitHub release at https://github.com/kanbn/kan/releases/tag/v0.5.5 and implemented in commit 53397d8e81dc1494d94132848c1f0416f1152bd7 (https://github.com/kanbn/kan/commit/53397d8e81dc1494d94132848c1f0416f1152bd7). As an interim workaround until upgrading is possible, block or restrict access to the /api/download/attatchment endpoint at the reverse proxy level using nginx, Cloudflare, or similar web application firewall solutions. Additionally, implement network segmentation to limit the server's ability to access internal networks and cloud metadata endpoints, and consider implementing egress filtering to restrict outbound connections from the Kan application server to only necessary destinations.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability affects Kan (CPE: cpe:2.3:a:kanbn:kan:*:*:*:*:*:*:*:*), an open-source project management application. The root cause is CWE-918 (Server-Side Request Forgery), where the /api/download/attatchment endpoint accepts a user-controlled URL parameter and passes it directly to a server-side fetch() function without validation or authentication checks. This allows attackers to abuse the server as a proxy to make HTTP requests to arbitrary destinations. The server returns the full response body, enabling information disclosure from internal network resources that would normally be inaccessible from external networks, including cloud provider metadata services, internal APIs, databases, and other backend systems on private network segments.
Know when Kan gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
DescriptionGitHub Advisory
Kan is an open-source project management tool. In versions 0.5.4 and below, the /api/download/attatchment endpoint has no authentication and no URL validation. The Attachment Download endpoint accepts a user-supplied URL query parameter and passes it directly to fetch() server-side, and returns the full response body. An unauthenticated attacker can use this to make HTTP requests from the server to internal services, cloud metadata endpoints, or private network resources. This issue has been fixed in version 0.5.5. To workaround this issue, block or restrict access to /api/download/attatchment at the reverse proxy level (nginx, Cloudflare, etc.).
Executive ViewAI
An unauthenticated vulnerability in Kan project management tool (versions 0.5.4 and below) allows attackers to access internal systems and cloud credentials without authentication, creating a direct path to data theft and infrastructure compromise. Any organization running affected Kan versions faces immediate risk of credential exposure and lateral movement into internal networks.
Implement Web Application Firewall (WAF) rules to block unauthenticated requests to /api/download/attachment endpoint; segment Kan servers on isolated networks with restricted egress to internal services and cloud metadata endpoints (169.254.169.254); disable the attachment download feature if operationally feasible; enforce mutual TLS authentication at network boundary; implement egress filtering to prevent server-to-cloud-metadata communication; monitor and log all outbound requests from Kan servers for anomalies.
Threat Intelligence Overview
NVD
CVE.org
EPSS
GitHub
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Affected Products (CPE)GitHub Advisory
Related Vulnerabilities in SSRF and Server-Side Request Forgery
View all 2Unauthenticated server-side request forgery in Kan 0.5.5 through 0.6.0 allows remote attackers to make the server issue
Guest-level users on kan through 0.6.0 can create boards they are not entitled to create by invoking the GitHub project
Exploit-DB