CVE-2026-103504

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3% (17th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS

Also known asEUVD-2026-93914 (ENISA EUVD)Source: ENISA EUVD

8.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: 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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

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
Web page

Gitea 28.0.0 is released | Gitea Blog

https://blog.gitea.com/release-of-28.0.0/
GitHub pull request

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
GitHub advisoryMentions 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 8× in last 7d / 44× 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.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-27 11:20 UTCEG score recompute
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-25 14:56 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-18 05:09 UTCEG score recompute
  20. 2026-10-17 19:43 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  24. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  25. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
Show 19 more
  1. 2026-10-12 16:40 UTCEG score recompute
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-11 20:15 UTCEG score recompute
  4. 2026-10-11 18:28 UTCEG score recompute
  5. 2026-10-11 14:07 UTCEG score recompute
  6. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-10-11 01:28 UTCEG score recompute
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  9. 2026-10-10 00:04 UTCEG score recompute
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-08 22:44 UTCEG score recompute
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-08 10:05 UTCEG score recompute
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-07 20:22 UTCEG score recomputeFirst assessed: 8.1 HIGH
  16. 2026-10-07 20:21 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  17. 2026-10-06 20:31 UTCNVD update
  18. 2026-10-06 19:32 UTCEG score recompute
  19. 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-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-103504 published?
The CVE record for CVE-2026-103504 was published on October 6, 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 October 7, 2026; the record at its source may have been updated since.
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 (17th 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