CVE-2026-114199

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

GHSA-jr76-w9m3-3p68 ↗EUVD-2026-114793 ↗

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-3220Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/gitea.dev
cvss4.0ethiack provisional
1h 58msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h40m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Gitea's contribution heatmap API could expose aggregate contribution counts and short time intervals associated with private repository activity. An attacker needs possession of a user's public-only access token; repository names and repository contents are not exposed.

mitigation

Upgrade gitea.dev to version 28.3.0. Revoke and reissue public-only tokens that may have been exposed until the update is complete.

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.
contextual
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
20m
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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

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-114199

{
  "etk_id": "ETK-2026-3220",
  "cve_id": "CVE-2026-114199",
  "display_id": "CVE-2026-114199",
  "ghsa_id": "GHSA-jr76-w9m3-3p68",
  "euvd_id": "EUVD-2026-114793",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Private activity disclosure in Gitea contribution heatmaps",
  "summary": "Gitea's contribution heatmap API could expose aggregate contribution counts and short time intervals associated with private repository activity. An attacker needs possession of a user's public-only access token; repository names and repository contents are not exposed.",
  "mitigation": "Upgrade gitea.dev to version 28.3.0. Revoke and reissue public-only tokens that may have been exposed until the update is complete.",
  "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": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.941426933333332,
  "t0_at": "2026-11-01T09:48:33.765000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-01T09:48:33.765000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-01T09:48:33.765000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114199"
    }
  }
}

published 2026-11-01 10:08Z
last change 2026-11-01 11:53Z

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.