← back to feed
ETK-2026-1030Zero's internal tracking ID, independent of the CVE number.

ETK-2026-1030Zero's internal tracking ID, independent of the CVE number.

validatedZero produced an exploit or a check.

GHSA-wf2j-5mc7-5c4w ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−12dkevAttacks confirmed in the real world.
uptime-kuma <=2.5.3
fixed in 2.5.4
CWE-400 Uncontrolled Resource Consumption
ETK-2026-1030Zero's internal tracking ID, independent of the CVE number., no cve assigned
cvss7.5cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
−12dTTV
11mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org, not yet published
trigger signal −12dpublic poc−12dcheck availableagent stopped
−10d
−5d
0

description

Uptime Kuma versions before 2.5.4 process costly badge-ping requests for attacker-controlled monitor identifiers before rejecting unavailable monitors. An unauthenticated remote attacker able to reach the public badge endpoint can exhaust service resources and disrupt the application, with degraded availability potentially continuing after request traffic stops.

mitigation

Upgrade uptime-kuma to version 2.5.4 or later. Until upgraded, restrict access to the badge endpoint and rate-limit requests to it at a reverse proxy or gateway.

fixed in 2.5.4

check
available
exploit
no
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.
–
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−12d
Δ to kevAttacks confirmed in the real world.
–

outcome

Check only, differential: the check fires on the vulnerable build and is 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-09 02:30Z
  2. 2026-10-09 02:30Z

this entry in the feed

GET /api/v1/feed/ETK-2026-1030

{
  "etk_id": "ETK-2026-1030",
  "cve_id": null,
  "display_id": "ETK-2026-1030",
  "ghsa_id": "GHSA-wf2j-5mc7-5c4w",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Unauthenticated resource exhaustion in uptime-kuma badge API",
  "summary": "Uptime Kuma versions before 2.5.4 process costly badge-ping requests for attacker-controlled monitor identifiers before rejecting unavailable monitors. An unauthenticated remote attacker able to reach the public badge endpoint can exhaust service resources and disrupt the application, with degraded availability potentially continuing after request traffic stops.",
  "mitigation": "Upgrade uptime-kuma to version 2.5.4 or later. Until upgraded, restrict access to the badge endpoint and rate-limit requests to it at a reverse proxy or gateway.",
  "vendor": null,
  "product": "uptime-kuma",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<=2.5.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.5.4"
      ],
      "package_name": "uptime-kuma",
      "purl": null
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 11.00588785,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-10-09T03:08:54.087853+00:00",
      "days": -12.071236400046296,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:51:28.934387+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-09T02:30:47+00:00",
      "days": -12.097707324270834,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:51:28.934387+00:00",
      "url": "https://github.com/louislam/uptime-kuma/security/advisories/GHSA-wf2j-5mc7-5c4w"
    },
    "trigger_signal": {
      "at": "2026-10-09T02:30:47+00:00",
      "days": -12.097707324270834,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:51:28.934387+00:00",
      "url": "https://github.com/louislam/uptime-kuma/security/advisories/GHSA-wf2j-5mc7-5c4w"
    }
  }
}

published 2026-10-09 02:57Z
last change 2026-10-21 04:45Z

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.