CVE-2026-28740

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Gitea versions up to and including 1.26.2 allow Git LFS object reuse to authorize private source objects for users who have repository access but lack Code-unit access.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (4)

Auto-updated Jul 3, 2026
Patch available. Sources: github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Git LFS object reuse allows non-Code access to authorize private source objects · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-2m9v-5q2g-58vq
GitHub release Patch Available

v1.26.3

Patch available: go-gitea/gitea v1.26.3

https://github.com/go-gitea/gitea/releases/tag/v1.26.3
GitHub pull request

fix(lfs): require Code-unit access for cross-repo LFS object reuse (#38006)

Fix merged in go-gitea/gitea PR #38050 on 2026-06-10 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/38050
Web page

Gitea 1.26.3 and 1.26.4 are released | Gitea Blog

https://blog.gitea.com/release-of-1.26.3-and-1.26.4/

Vendor Advisories for CVE-2026-28740(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
code.gitea.io/gitea—
  • every version up to 1.26.3: fixed in 1.26.3
—
gitea.dev—
  • every version up to 1.26.3: fixed in 1.26.3
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 140 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 45 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:58 UTCEG score recompute
  2. 2026-10-11 17:12 UTCEG score recompute
  3. 2026-10-11 14:42 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-09-23 06:34 UTCEG score recompute
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-09-18 06:11 UTCEG score recompute
  22. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-09-14 00:02 UTCEG score recompute
Show 70 more
  1. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-09-13 08:54 UTCEG score recompute
  3. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-09-12 14:01 UTCEG score recompute
  5. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-09-06 14:17 UTCEG score recompute
  10. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-09-05 23:40 UTCEG score recompute
  12. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-08-30 23:59 UTCEG score recompute
  17. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-08-30 11:18 UTCEG score recompute
  19. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-08-27 22:11 UTCEG score recompute
  22. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-08-27 03:12 UTCEG score recompute
  24. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-08-26 14:31 UTCEG score recompute
  26. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-08-24 22:53 UTCEG score recompute
  28. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  29. 2026-08-24 10:11 UTCEG score recompute
  30. 2026-08-23 07:44 UTCEG score recompute
  31. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  32. 2026-08-22 06:25 UTCEG score recompute
  33. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  34. 2026-08-21 04:59 UTCEG score recompute
  35. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  36. 2026-08-20 03:41 UTCEG score recompute
  37. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  38. 2026-08-19 00:56 UTCEG score recompute
  39. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  40. 2026-08-17 23:15 UTCEG score recompute
  41. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  42. 2026-08-16 21:53 UTCEG score recompute
  43. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  44. 2026-08-16 09:13 UTCEG score recompute
  45. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  46. 2026-08-15 07:55 UTCEG score recompute
  47. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  48. 2026-08-14 06:04 UTCEG score recompute
  49. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  50. 2026-08-12 16:07 UTCEG score recompute
  51. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  52. 2026-08-11 14:49 UTCEG score recompute
  53. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  54. 2026-08-11 02:09 UTCEG score recompute
  55. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  56. 2026-08-10 00:50 UTCEG score recompute
  57. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  58. 2026-08-08 23:33 UTCEG score recompute
  59. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  60. 2026-08-07 22:14 UTCEG score recompute
  61. 2026-08-06 20:56 UTCEG score recompute
  62. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  63. 2026-08-05 19:38 UTCEG score recompute
  64. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  65. 2026-08-04 16:26 UTCEG score recompute
  66. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  67. 2026-08-03 15:08 UTCEG score recompute
  68. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  69. 2026-08-01 12:29 UTCEG score recompute
  70. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 18th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-28740?
CVE-2026-28740 is a high-severity vulnerability; its CVE record was published on July 3, 2026. Gitea versions up to and including 1.26.2 allow Git LFS object reuse to authorize private source objects for users who have repository access but lack Code-unit access.
When was the CVE record for CVE-2026-28740 published?
The CVE record for CVE-2026-28740 was published on July 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 7, 2026; the record at its source may have been updated since.
Is CVE-2026-28740 actively exploited?
CVE-2026-28740 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-28740?
CVE-2026-28740 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-28740?
A fix for CVE-2026-28740 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-28740 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-28740

Explore →

Is Your Infrastructure Affected by CVE-2026-28740?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs