CVE-2026-117649

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

GHSA-p86q-78gw-8f3f ↗EUVD-2026-114799 ↗

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 <= 28.2.0
fixed in 28.3.0
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-3221Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/gitea.dev
cvss4.0ethiack provisional
2h 53msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h37m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Gitea issue timelines and issue pages can expose metadata from an inaccessible issue when it is configured as a dependency of an issue the reader can view. An attacker needs access to the readable issue; affected public issues may expose linked private-issue information to anonymous visitors.

mitigation

Upgrade Gitea to version 28.3.0. Until upgraded, review and remove dependency links between publicly readable issues and issues with restricted visibility.

fixed in 28.3.0

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-01 09:48Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-01 09:48Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3221",
  "cve_id": "CVE-2026-117649",
  "display_id": "CVE-2026-117649",
  "ghsa_id": "GHSA-p86q-78gw-8f3f",
  "euvd_id": "EUVD-2026-114799",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Gitea issue dependency authorization flaw",
  "summary": "Gitea issue timelines and issue pages can expose metadata from an inaccessible issue when it is configured as a dependency of an issue the reader can view. An attacker needs access to the readable issue; affected public issues may expose linked private-issue information to anonymous visitors.",
  "mitigation": "Upgrade Gitea to version 28.3.0. Until upgraded, review and remove dependency links between publicly readable issues and issues with restricted visibility.",
  "vendor": "Gitea",
  "product": "Gitea",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 28.2.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "28.3.0"
      ],
      "package_name": "gitea.dev",
      "purl": "pkg:golang/gitea.dev"
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 4,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.92430485,
  "t0_at": "2026-11-01T09:48:43.592000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-01T09:48:43.592000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-01T09:48:43.592000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-117649"
    }
  }
}

published 2026-11-01 10:08Z
last change 2026-11-01 13: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.