CVE-2026-97204

validatedZero produced an exploit or a check.

GHSA-fxq4-gr55-7x5g ↗EUVD-2026-103992 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Gitea <= 28.1.0
fixed in 28.2.0
CWE-863 Incorrect Authorization
ETK-2026-2265Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/gitea.dev
+2.3dTTV
15mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+2.3dagent stopped
0
+1d
+2d

description

Gitea versions reported through 28.1.0 may incorrectly authorize label deletion across repository and organization boundaries. A user with write access to a repository's issues can remove organization labels when the relevant numeric identifiers overlap.

mitigation

Upgrade gitea.dev to 28.2.0 or later.

fixed in 28.2.0

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-18 19:00Z
Δ 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

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-18 19:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2265",
  "cve_id": "CVE-2026-97204",
  "display_id": "CVE-2026-97204",
  "ghsa_id": "GHSA-fxq4-gr55-7x5g",
  "euvd_id": "EUVD-2026-103992",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization flaw in Gitea label deletion",
  "summary": "Gitea versions reported through 28.1.0 may incorrectly authorize label deletion across repository and organization boundaries. A user with write access to a repository's issues can remove organization labels when the relevant numeric identifiers overlap.",
  "mitigation": "Upgrade gitea.dev to 28.2.0 or later.",
  "vendor": "Gitea",
  "product": "Gitea",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 28.1.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "28.2.0"
      ],
      "package_name": "gitea.dev",
      "purl": "pkg:golang/gitea.dev"
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 3.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 15.321996316666667,
  "t0_at": "2026-10-18T19:00:50.994000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-21T02:28:41.430500+00:00",
      "days": 2.3110004224537035,
      "is_lower_bound": false,
      "measured_at": "2026-10-18T19:00:50.994000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-18T19:00:50.994000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-18T19:00:50.994000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-97204"
    }
  }
}

published 2026-10-21 02:13Z
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.