The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository is archived. A user allowed to change issues of an archived repository could use the API to edit, close or delete issues, change labels and deadlines, add or delete tracked time and stopwatches, add reactions, change issue blocks, and pin issues, altering data that archiving is meant to freeze. Gitea 28.2.0 added the check to the issue edit, delete and label routes; Gitea 28.3.0 applies it to all modifying repository API requests.
CVE-2026-118504
MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3% (26th 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-114804 (ENISA EUVD)Source: ENISA EUVD
6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMmedium confidence
- EG Risk
- 29EG Risk 29/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)Severity65% × 45%Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.2% × 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 every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
- 26th
- 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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.5 MEDIUMCVSS-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. 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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
November 1, 2026
Last Modified
November 6, 2026
Advisory Details (7)
Auto-updated Nov 6, 2026Patch available. Sources: github, github_pr, github_release.
GitHub release Patch Available
v28.3.0
Patch available: go-gitea/gitea v28.3.0
https://github.com/go-gitea/gitea/releases/tag/v28.3.0GitHub pull request
fix: add missing access checks and size limits (#39942)
Fix merged in go-gitea/gitea PR #40085 on 2026-10-30 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/40085GitHub pull request
fix: add missing access checks and size limits
Fix merged in go-gitea/gitea PR #39942 on 2026-10-27 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/39942GitHub pull request
fix: add missing checks to several handlers and models (#39839)
Fix merged in go-gitea/gitea PR #39847 on 2026-10-18 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/39847GitHub pull request
fix: add missing checks to several handlers and models
Fix merged in go-gitea/gitea PR #39839 on 2026-10-18 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/39839GitHub advisoryMentions a patch (unverified)
API Issue Mutation Archive Restriction Bypass · Advisory · go-gitea/gitea · GitHub
https://github.com/go-gitea/gitea/security/advisories/GHSA-vmrc-8q2x-573xWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 17× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-11-06 15:18 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
- 2026-11-06 15:17 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
- 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-11-01 11:02 UTCENISA EUVD ID recordedEUVD-2026-114804 · Source: ENISA EUVD
- 2026-11-01 10:26 UTCNVD update
- 2026-11-01 09:52 UTCEchelonGraph re-scored
- 2026-11-01 09:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-118504?
CVE-2026-118504 is a medium-severity vulnerability; its CVE record was published on November 1, 2026. The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository is archived. A user allowed to change issues of an archived repository could use the API to edit, close or delete issues, change labels and…
When was the CVE record for CVE-2026-118504 published?
The CVE record for CVE-2026-118504 was published on November 1, 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 November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-118504 actively exploited?
CVE-2026-118504 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118504?
CVE-2026-118504 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-118504?
A fix for CVE-2026-118504 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-118504
Is Your Infrastructure Affected by CVE-2026-118504?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.