CVE-2026-129525

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3% (19th 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-126133 (ENISA EUVD)Source: ENISA EUVD

5.4EG
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: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A user who can read a repository's issues but not its pull requests could read pull request data through the issue sub-resources of the API (timeline, attachments, labels, subscriptions, tracked times and reactions), and list pull requests through the repository's issue search and milestone pages; the same applied in the other direction. These endpoints now check read access to the unit the item belongs to. The API endpoints were fixed in 28.2.0 and 28.3.0, the search and milestone pages in 28.4.0.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 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
19th
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 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 15, 2026

Last Modified

November 16, 2026

Advisory Details (9)

Auto-updated Nov 16, 2026
Patch available. Sources: github, github_pr, github_release.
GitHub release Patch Available

v28.4.0

Patch available: go-gitea/gitea v28.4.0

https://github.com/go-gitea/gitea/releases/tag/v28.4.0
Web page

Gitea 28.4.0 is released | Gitea Blog

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

fix(issues): hide unreadable issue types in search and milestone views (#40192)

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

https://github.com/go-gitea/gitea/pull/40375
GitHub pull request

fix(issues): hide unreadable issue types in search and milestone views

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

https://github.com/go-gitea/gitea/pull/40192
GitHub pull request

fix(api): check unit read permission in issue sub-resource endpoints (#39885)

Fix merged in go-gitea/gitea PR #39938 on 2026-10-22 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/39938
GitHub pull request

fix(api): check unit read permission in issue sub-resource endpoints

Fix merged in go-gitea/gitea PR #39885 on 2026-10-22 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/39885
GitHub 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/39847
GitHub 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/39839
GitHub advisoryMentions a patch (unverified)

Issues-only members can read pull request data through /issues/{index} · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-qrrc-h266-v49p

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  6. 2026-11-16 21:29 UTCEchelonGraph re-scoredFirst assessed: 5.4 MEDIUM
  7. 2026-11-16 21:28 UTCMITRE cvelistV5CVSS v3 → 5.4 · severity → MEDIUM
  8. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-11-15 22:02 UTCENISA EUVD ID recordedEUVD-2026-126133 · Source: ENISA EUVD
  10. 2026-11-15 21:19 UTCEchelonGraph re-scored
  11. 2026-11-15 21:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129525?
CVE-2026-129525 is a medium-severity vulnerability; its CVE record was published on November 15, 2026. Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A user who can read a repository's issues but not its pull requests could read pull request data through the issue sub-resources of the API (timeline, attachments, labels,…
When was the CVE record for CVE-2026-129525 published?
The CVE record for CVE-2026-129525 was published on November 15, 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 16, 2026; the record at its source may have been updated since.
Is CVE-2026-129525 actively exploited?
CVE-2026-129525 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129525?
CVE-2026-129525 has a CVSS v3.1 base score of 5.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-129525?
A fix for CVE-2026-129525 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-129525

Explore →

Is Your Infrastructure Affected by CVE-2026-129525?

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