← back to feed
CVE-2026-110628

CVE-2026-110628

validatedZero produced an exploit or a check.

GHSA-8p5c-vr7c-5g49 ↗EUVD-2026-101256 ↗

check availableZero validated a working check for it.proven exploitableZero has validated a full working exploit.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
kanbn kan
fixed in >= v5.5.0
CWE-918 Server-Side Request Forgery (SSRF)
ETK-2026-1582Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.2cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
+1h44mTTV
41mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck + exploit+104m
0
+30min
+60min
+90min

description

Kan 0.5.5 through 0.6.0 exposes an SSRF condition in its attachment download API. An unauthenticated remote attacker may cause the server to make requests to internal network services or cloud metadata endpoints when S3_ENDPOINT is not configured.

mitigation

Set S3_ENDPOINT to avoid the documented vulnerable configuration, and restrict unauthenticated access to the attachment download API. Apply network egress controls that block access to internal addresses and metadata services from the Kan deployment.

fixed in >= v5.5.0

check
available
exploit
yes
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.43%35th percentile
agent run time
41m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 14:17Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Differential: the exploit fired on the vulnerable build and stayed silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-14 14:17Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-110628

this entry in the feed

GET /api/v1/feed/CVE-2026-110628

{
  "etk_id": "ETK-2026-1582",
  "cve_id": "CVE-2026-110628",
  "display_id": "CVE-2026-110628",
  "ghsa_id": "GHSA-8p5c-vr7c-5g49",
  "euvd_id": "EUVD-2026-101256",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated server-side request forgery in Kan",
  "summary": "Kan 0.5.5 through 0.6.0 exposes an SSRF condition in its attachment download API. An unauthenticated remote attacker may cause the server to make requests to internal network services or cloud metadata endpoints when S3_ENDPOINT is not configured.",
  "mitigation": "Set S3_ENDPOINT to avoid the documented vulnerable configuration, and restrict unauthenticated access to the attachment download API. Apply network egress controls that block access to internal addresses and metadata services from the Kan deployment.",
  "vendor": "kanbn",
  "product": "kan",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 53397d8"
      ],
      "ecosystem": "https://github.com/kanbn/kan",
      "fixed_versions": [
        ">= v5.5.0"
      ],
      "package_name": "Kan",
      "purl": null
    }
  ],
  "cwes": [
    918
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N",
  "epss_score": 0.0043,
  "epss_percentile": 0.3544,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": true,
  "pipeline_minutes": 41.15509415,
  "t0_at": "2026-10-14T14:17:03.232000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-14T16:01:08.215773+00:00",
      "days": 0.0722799047800926,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T14:17:03.232000+00:00",
      "url": null
    },
    "exploit": {
      "at": "2026-10-14T16:01:08.215773+00:00",
      "days": 0.0722799047800926,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T14:17:03.232000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-14T14:17:03.232000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T14:17:03.232000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110628"
    }
  }
}

published 2026-10-14 15:19Z
last change 2026-10-21 05:00Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.