CVE-2026-103504

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). 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: cisa-adp, epss
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Changing an organization team's permission through the API with only the permission field did not rebuild the team's per-unit access, and the requested level was not applied as a cap. After an organization owner demoted a team, for example from admin to read, the team's members kept their previous unit permissions, including write access to the team's repositories. The web form was not affected.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 6, 2026

Last Modified

October 7, 2026

Advisory Details (4)

Auto-updated Oct 7, 2026
Patch available. Sources: github, github_pr, github_release.
github_release Patch Available

v28.0.0

Patch available: go-gitea/gitea v28.0.0

https://github.com/go-gitea/gitea/releases/tag/v28.0.0
generic

Gitea 28.0.0 is released | Gitea Blog

https://blog.gitea.com/release-of-28.0.0/
github_pr

enhance: inherit team access for all units

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

https://github.com/go-gitea/gitea/pull/38938
githubMentions a patch (unverified)

API team demotion does not reset unit permissions · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-x8c3-3rp8-2j46

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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-10-10 00:04 UTCEG score recompute
  2. 2026-10-09 20:06 UTCEPSS rescore
  3. 2026-10-08 22:44 UTCEG score recompute
  4. 2026-10-08 17:11 UTCEPSS rescore
  5. 2026-10-08 10:05 UTCEG score recompute
  6. 2026-10-07 23:47 UTCEPSS rescore
  7. 2026-10-07 20:22 UTCEG score recompute▲ 8.10
  8. 2026-10-07 20:21 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  9. 2026-10-06 20:31 UTCNVD update
  10. 2026-10-06 19:32 UTCEG score recompute
  11. 2026-10-06 19:31 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-103504?
CVE-2026-103504 is a high vulnerability published on October 6, 2026. Changing an organization team's permission through the API with only the permission field did not rebuild the team's per-unit access, and the requested level was not applied as a cap. After an organization owner demoted a team, for example from admin to read, the team's members kept their previous…
When was CVE-2026-103504 disclosed?
CVE-2026-103504 was first published on October 6, 2026, with the most recent update on October 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-103504 actively exploited?
CVE-2026-103504 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103504?
CVE-2026-103504 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-103504?
A fix for CVE-2026-103504 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-103504?

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

Book a Demo →Browse All CVEs