Skip to content
Wednesday, October 14, 2026AboutContactRSS
Vulnerabilities

Critical-Severity Server-Side Request Forgery Flaw in kanbn kan Tracked as CVE-2026-110628

A newly published critical vulnerability in kanbn kan carries a CVSS score of 9.2. Here is what is affected and how to respond.

Illustration: A minimalist white task board sits on a desk, its blank sticky notes arranged in neat columns.
AI-generated illustration: Threat Times

Key points

  • CVE-2026-110628 affects kanbn kan.
  • CVSS 9.2 (Critical).
  • No exploitation confirmed yet.

A critical server-side request forgery tracked as CVE-2026-110628 has been published in the National Vulnerability Database for kanbn kan, with a CVSS base score of 9.2.

At a glance

CVE
CVE-2026-110628
Product
kanbn kan
CVSS
9.2 Critical
Weakness
server-side request forgery
Exploited
No known exploitation

What is the vulnerability?

The NVD entry states: Kan 0.5.5 through 0.6.0 contains an unauthenticated server-side request forgery vulnerability in the /api/download/attatchment route due to an incomplete fix for CVE-2026-32255. When S3_ENDPOINT is unset, attackers can pass arbitrary url query parameters to fetch() to read internal services, localhost ports, and cloud instance metadata.

Affected versions

VendorProductVersions
Kanbnkanup to 0.6.0

Is it being exploited?

There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.

What should you do?

  • Identify whether the affected product and versions run in your environment.
  • Apply the vendor update listed in the advisory as soon as it is available.
  • Limit network exposure of the affected service until it is patched.
  • Monitor the vendor advisory for updated guidance or exploitation reports.

What to do and how to stay safe: CVE-2026-110628

  • Vulnerability severity scores ignore your specific architecture and context.
  • Exploitability depends on network exposure and user behavior, not just code flaws.
  • Prioritization requires continuous asset inventory and threat intelligence alignment.

Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.

Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is CVE-2026-110628?

CVE-2026-110628 is a server-side request forgery vulnerability in kanbn kan.

How severe is CVE-2026-110628?

It has a CVSS score of 9.2 Critical.

Is CVE-2026-110628 being exploited?

There is no public confirmation of exploitation at the time of publication.

Sources

  1. NVD — CVE-2026-110628
  2. Reference
  3. Reference
  4. Reference
CVE-2026-110628kanbn kanCritical severity
Related articles