CVE-2026-27771

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 40.7%, top 2% 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.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 41%CVSS: 8.2Exploit: 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 have insufficient permission checks for Composer package source links, which can expose private or internal package source information.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
98.5%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (4)

Auto-updated Jul 3, 2026
Patch available. Sources: github_release, github, github_pr.
github Patch Available

Critical Vulnerability - Already emailed · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-8qw8-rq86-9pc2
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(packages): Add label for private and internal package and fix composor package source permission check

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

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

Gitea 1.26.2 is released | Gitea Blog

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCportbuster1337/CVE-2026-27771
    First seen May 27, 2026

    CVE-2026-27771 - Gitea/Forgejo Container Registry Auth Bypass Exploit PoC - Pull private container images without authentication

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-27771.yaml
    First seen Jan 1, 2026

    Gitea Container Registry - Unauthorized Private Image Access

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-27771?
CVE-2026-27771 is a high vulnerability published on July 3, 2026. Gitea versions up to and including 1.26.1 have insufficient permission checks for Composer package source links, which can expose private or internal package source information.
When was CVE-2026-27771 disclosed?
CVE-2026-27771 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-27771 actively exploited?
CVE-2026-27771 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-27771?
CVE-2026-27771 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-27771?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27771, 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-27771

Explore →

Is Your Infrastructure Affected by CVE-2026-27771?

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

Start Free Scan →Browse All CVEs