CVE-2026-27761

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% 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
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: 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.2 allow repository RSS and Atom feed endpoints to bypass API access token scope checks, exposing private repository commit data to tokens without the required repository scope.

CVSS v3
4.3
EG Score
4.3(medium)
EPSS
28.8%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (4)

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

API access token scope enforcement bypass on repository RSS/Atom feed endpoints leaks private repository commit data · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-3pww-vcvm-3gmj
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_pr

fix: Various sec fixes (#38108)

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

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

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/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 24× 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-14 00:34 UTCEG score recompute
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 02:36 UTCEG score recompute
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-12 04:37 UTCEG score recompute
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 06:40 UTCEG score recompute
  10. 2026-07-10 08:40 UTCEG score recompute
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 10:42 UTCEG score recompute
  13. 2026-07-08 12:41 UTCEG score recompute
  14. 2026-07-07 14:40 UTCEG score recompute
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 16:26 UTCEG score recompute
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 18:27 UTCEG score recompute
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 20:28 UTCEG score recompute
  23. 2026-07-03 22:30 UTCEG score recompute
  24. 2026-07-03 22:27 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-27761?
CVE-2026-27761 is a medium vulnerability published on July 3, 2026. Gitea versions up to and including 1.26.2 allow repository RSS and Atom feed endpoints to bypass API access token scope checks, exposing private repository commit data to tokens without the required repository scope.
When was CVE-2026-27761 disclosed?
CVE-2026-27761 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27761 actively exploited?
CVE-2026-27761 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-27761?
CVE-2026-27761 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-27761?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27761, 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

Explore the affected products and dependency analysis for CVE-2026-27761

Explore →

Is Your Infrastructure Affected by CVE-2026-27761?

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

Start Free Scan →Browse All CVEs