VulnerabilityPublished 18 Mar 2026

CVE-2026-32255: kanbn kan · Server-Side Request Forgery (SSRF)

Affects kanbn kanSource CVE Database V5

Compare

Not known to be exploited · public detection template (Nuclei) · 26% EPSS · CVSS 8.6 High : upgrade to 0.5.5 soon.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 26.3% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.5.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Mar 2026
Detectable: evidence found.
nuclei template: Kan <= 0.5.4 - Server-Side Request Forgery
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade kan and kanbn/kan to 0.5.5.

Affected software

Product	Affected	Fixed in
kanbnkan	Affected <0.5.5	Fixed in 0.5.5
GitHubkanbn/kan`pkg:github/kanbn/kan`Other threats	Affected <0.5.5	Fixed in 0.5.5

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

AI-suggested

Upgrade kan to version 0.5.5 or later immediately, as this version contains the fix for the SSRF vulnerability.
Until the upgrade can be performed, implement strict access controls at the reverse proxy or firewall level to block or restrict access to the /api/download/attatchment endpoint. This can be done by IP whitelisting, authentication enforcement, or complete blocking if the endpoint is not required.
Employ network segmentation to limit the kan server's ability to reach sensitive internal services and cloud metadata endpoints, reducing the potential impact of SSRF exploitation.
Monitor server logs for unusual outbound requests originating from the kan server, especially to internal IP ranges or cloud metadata URLs, to detect potential exploitation attempts.
Review and harden cloud instance metadata service access policies, such as enabling metadata service version 2 (IMDSv2) on AWS, to mitigate SSRF risks.
Conduct a security audit of other endpoints in kan for similar SSRF or injection vulnerabilities.
Educate development teams on secure coding practices, including input validation and authentication enforcement on sensitive endpoints.

Description

CVE-2026-32255 is a high-severity Server-Side Request Forgery (SSRF) vulnerability affecting kanbn's open-source project management tool, kan, in versions prior to 0.5.5. The vulnerability exists in the /api/download/attatchment endpoint, which lacks authentication and URL validation, allowing unauthenticated attackers to supply arbitrary URLs that the server fetches and returns. This can be exploited to access internal services, cloud metadata endpoints, or private network resources, potentially exposing sensitive information. No user interaction or authentication is required, and the vulnerability has a CVSS score of 8.6. The issue is fixed in version 0.5.5, and as a mitigation, blocking or restricting access to the vulnerable endpoint at the reverse proxy level is recommended.

Impact

The primary impact of this SSRF vulnerability is unauthorized access to internal network resources and cloud metadata services, which can lead to significant information disclosure. Attackers can retrieve sensitive data such as internal API endpoints, configuration files, or cloud instance credentials, potentially enabling further attacks like privilege escalation or lateral movement within the victim's environment. Since the vulnerability requires no authentication or user interaction, it can be exploited remotely by any attacker with network access to the kan server. Organizations using affected versions of kan may face data breaches, exposure of confidential project management information, and compromise of cloud infrastructure credentials. The scope of impact is broad because many organizations use project management tools like kanbn, and the vulnerability affects all deployments running versions below 0.5.5. Additionally, the ability to access cloud metadata endpoints can lead to full cloud account compromise. The absence of known exploits in the wild currently reduces immediate risk but does not diminish the urgency of remediation given the vulnerability's severity and ease of exploitation.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

CVE-2026-32255: kanbn kan · Server-Side Request Forgery (SSRF)

Exploitation evidence

What to do

Affected software

Description

Impact

Nuclei detection templates

Proofs of concept on GitHub

References

Community reviews

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 01:10 UTC

Public exploits and detectiona Nuclei detection template, GitHub proofs of concept

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats