CVE-2026-28744

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Gitea versions up to and including 1.26.1 allow Git smart HTTP requests authenticated with bearer tokens to bypass repository token scope checks.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
26.3%
KEV
Not listed

Published

June 16, 2026

Last Modified

July 6, 2026

Advisory Details (4)

Auto-updated Jul 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_pr.
github Patch Available🟡 PoC Available

Git Smart HTTP Skips Repository Token Scopes for Bearer Tokens · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-cc8w-r4qh-3v65
github_release Patch Available

v1.26.2

Patch available: go-gitea/gitea v1.26.2

https://github.com/go-gitea/gitea/releases/tag/v1.26.2
github_pr

fix(git): Fix smart http request scope bug

Fix merged in go-gitea/gitea PR #37583 on 2026-05-08 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/37583
generic

Gitea 1.26.2 is released | Gitea Blog

https://blog.gitea.com/release-of-1.26.2/

Vendor Advisories for CVE-2026-28744(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
code.gitea.io/gitea—1.26.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-06 22:55 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 22:17 UTCEG score recompute
  7. 2026-07-05 10:00 UTCEG score recompute
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 21:26 UTCEG score recompute
  10. 2026-07-04 08:59 UTCEG score recompute
  11. 2026-07-03 16:16 UTCEG score recompute
  12. 2026-07-03 03:59 UTCEG score recompute
  13. 2026-07-02 15:21 UTCEG score recompute
  14. 2026-07-02 03:03 UTCEG score recompute
  15. 2026-07-01 14:45 UTCEG score recompute
  16. 2026-07-01 02:28 UTCEG score recompute
  17. 2026-06-30 14:11 UTCEG score recompute
  18. 2026-06-30 01:51 UTCEG score recompute
  19. 2026-06-29 13:33 UTCEG score recompute
  20. 2026-06-29 01:16 UTCEG score recompute
  21. 2026-06-28 12:57 UTCEG score recompute
  22. 2026-06-28 00:40 UTCEG score recompute
  23. 2026-06-27 12:23 UTCEG score recompute
  24. 2026-06-27 00:05 UTCEG score recompute
  25. 2026-06-26 11:48 UTCEG score recompute
Show 18 more
  1. 2026-06-25 20:30 UTCEG score recompute
  2. 2026-06-25 08:12 UTCEG score recompute
  3. 2026-06-24 19:55 UTCEG score recompute
  4. 2026-06-24 04:51 UTCEG score recompute
  5. 2026-06-23 16:24 UTCEG score recompute
  6. 2026-06-23 04:06 UTCEG score recompute
  7. 2026-06-22 15:48 UTCEG score recompute
  8. 2026-06-22 03:24 UTCEG score recompute
  9. 2026-06-21 14:35 UTCEG score recompute
  10. 2026-06-21 02:18 UTCEG score recompute
  11. 2026-06-20 13:59 UTCEG score recompute
  12. 2026-06-20 01:38 UTCEG score recompute
  13. 2026-06-19 13:21 UTCEG score recompute
  14. 2026-06-19 01:00 UTCEG score recompute
  15. 2026-06-18 12:39 UTCEG score recompute
  16. 2026-06-18 00:22 UTCEG score recompute
  17. 2026-06-17 12:02 UTCEG score recompute
  18. 2026-06-16 23:44 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-28744?
CVE-2026-28744 is a high vulnerability published on June 16, 2026. Gitea versions up to and including 1.26.1 allow Git smart HTTP requests authenticated with bearer tokens to bypass repository token scope checks.
When was CVE-2026-28744 disclosed?
CVE-2026-28744 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28744 actively exploited?
CVE-2026-28744 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-28744?
CVE-2026-28744 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-28744?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28744, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-28744?

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

Start Free Scan →Browse All CVEs