CVE-2026-97859

waiting for further signalsZero needs more public information before it can validate it.

GHSA-xvfh-qwmh-f92w ↗EUVD-2026-103993 ↗

no check availablenot proven exploitable
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 <= 1.27.2
fixed in 1.27.3
CWE-862 Missing Authorization
ETK-2026-2500Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/gitea.dev
33msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+98h06m
0
+2h
+4h
+6h
+8h
+10h

description

Gitea user API routes can fail to enforce visibility restrictions for target accounts. An authenticated attacker may obtain user relationship data, repository-interest information, or published key material for accounts they should not be able to view. Exploitation requires an authenticated Gitea account.

mitigation

Upgrade Gitea to 1.27.3 or 28.0.0, as appropriate for your release line. Restrict access to the affected user API endpoints until upgrades are complete.

fixed in 1.27.3

check
no
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.
contextual
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
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-18 19:01Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-18 19:01Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2500",
  "cve_id": "CVE-2026-97859",
  "display_id": "CVE-2026-97859",
  "ghsa_id": "GHSA-xvfh-qwmh-f92w",
  "euvd_id": "EUVD-2026-103993",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Gitea user API routes",
  "summary": "Gitea user API routes can fail to enforce visibility restrictions for target accounts. An authenticated attacker may obtain user relationship data, repository-interest information, or published key material for accounts they should not be able to view. Exploitation requires an authenticated Gitea account.",
  "mitigation": "Upgrade Gitea to 1.27.3 or 28.0.0, as appropriate for your release line. Restrict access to the affected user API endpoints until upgrades are complete.",
  "vendor": "Gitea",
  "product": "Gitea",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.27.2"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "1.27.3"
      ],
      "package_name": "gitea.dev",
      "purl": "pkg:golang/gitea.dev"
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 6.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.0938713,
  "t0_at": "2026-10-18T19:01:04.328000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-18T19:01:04.328000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-18T19:01:04.328000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-97859"
    }
  }
}

published 2026-10-22 20:53Z
last change 2026-10-22 21:37Z

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.