{"items":[{"id":"NVI-00016205","kind":"vulnerability","title":"Gitea: Git LFS object reuse allows non-Code access to authorize private source objects","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2m9v-5q2g-58vq","CVE-2026-28740"],"plain_summary":"GitHub lists this reviewed advisory for gitea.dev. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-450320fba63e5e79d7b92950f84c3870"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-21T20:29:44.000Z","value":"7.1 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-450320fba63e5e79d7b92950f84c3870"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-450320fba63e5e79d7b92950f84c3870","url":"https://github.com/advisories/GHSA-2m9v-5q2g-58vq","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2m9v-5q2g-58vq","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T22:34:39.734Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-450320fba63e5e79d7b92950f84c3870"],"technology":"gitea.dev","known_exclusions":[],"conditions_summary":"## Summary\n\nA user with Code write access to one repository may be able to associate an existing Git LFS object from a private source repository with their target repository, even when they do not have Code access to the source repository that currently owns the LFS object.\n\nThe issue appears to be caused by the source-object authorization check using broad repository accessibility instead of requiring Code-unit access to at least one repository that owns the requested LFS object.\n\n## Impact\n\nThis issue breaks the expected authorization boundary between repository units.\n\nA user who does not have Code access to a private source repository should not be able to reuse or associate Git LFS objects owned by that repository. However, because the source-object accessibility check accepts broad repository access, non-Code access such as Issues access may be sufficient for the LFS object to be treated as accessible.\n\nIf the reused object becomes downloadable through the attacker-controlled target repository after metadata association, this can result in cross-repository Git LFS content disclosure.\n\nThe target repository write authorization is still enforced. The problem is specifically in ","public_affected_ranges":["< 1.26.3"]}],"null_published_at":"2026-11-04T10:04:27.918Z","source_updated_at":"2026-07-21T20:29:44.000Z","source_disclosed_at":"2026-07-21T20:29:43.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-03T22:34:39.734Z"}],"next_cursor":null,"snapshot_revision":"42594"}