CVE-2026-120725

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

GHSA-8pmc-9g44-v9gw ↗EUVD-2026-126118 ↗

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.3.0
fixed in 28.4.0
CWE-306 Missing Authentication for Critical Function
ETK-2026-4551Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/gitea.dev
3d 00h 13msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h27m
+2h
+4h
+6h
+8h
+10h
+12h

description

Gitea instances with REQUIRE_SIGNIN_VIEW enabled may expose Git LFS endpoint responses for repositories that are not private. An unauthenticated party that knows a repository path and LFS object identifier may retrieve an object or determine whether it is present.

mitigation

Upgrade Gitea to version 28.4.0. Until upgraded, restrict access to Git LFS endpoints at the network or reverse-proxy layer.

fixed in 28.4.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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.27%18th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-15 21:13Z
Δ 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-15 21:13Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4551",
  "cve_id": "CVE-2026-120725",
  "display_id": "CVE-2026-120725",
  "ghsa_id": "GHSA-8pmc-9g44-v9gw",
  "euvd_id": "EUVD-2026-126118",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Gitea Git LFS endpoints",
  "summary": "Gitea instances with `REQUIRE_SIGNIN_VIEW` enabled may expose Git LFS endpoint responses for repositories that are not private. An unauthenticated party that knows a repository path and LFS object identifier may retrieve an object or determine whether it is present.",
  "mitigation": "Upgrade Gitea to version 28.4.0. Until upgraded, restrict access to Git LFS endpoints at the network or reverse-proxy layer.",
  "vendor": "Gitea",
  "product": "Gitea",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 28.3.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "28.4.0"
      ],
      "package_name": "gitea.dev",
      "purl": "pkg:golang/gitea.dev"
    }
  ],
  "cwes": [
    306
  ],
  "cvss_score": 3.7,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
  "epss_score": 0.0027,
  "epss_percentile": 0.1857,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.614988966666667,
  "t0_at": "2026-11-15T21:13:51.736000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-15T21:13:51.736000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-15T21:13:51.736000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-120725"
    }
  }
}

published 2026-11-15 21:28Z
last change 2026-11-18 20:02Z

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.