ApplicationsHigh 8.8Patch available
CVE-2026-125423
Race condition in Gitea initial repo allows overwrite of server hooks.
How scary is it?
updated 17 Nov 2026- No
Works without logging in1
Needs a login: a basic user account (CVSS PR:L).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
Proof-of-concept code is public2
1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list3
Not in the catalog as of our last sync.
Scare-o-meter
Act this week
Serious and within reach of attackers. Schedule the fix this week.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Public proof-of-concept code exists for a network-reachable flaw; CVSS 8.8.1 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run Gitea in an affected version< 28.4.0
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
The attacker has a user account
CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
Recommendation, AI-writtenUpgrade to Gitea v28.4.0+ immediately; restrict repo creation until patched.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
- CVSS
- 8.8Highscored by CISA
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 0.44%chance of exploitation in the next 30 daystop 62% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 15 Nov 2026analysed here 17 Nov 2026
Summary
Impact
Authenticated repo creator can overwrite server-side git hooks to execute commands as the Gitea system user.
Triage
- Exploitable
- At runtime
- Attack vector
- network
- Can a WAF block it?
- Partly. See why
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Gitea | < 28.4.0Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- Gitea (self-hosted) < 28.4.0
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
- CISA SSVC
- exploitation none, automatable no, technical impact totalAssessed by CISA 16 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 15 Nov 2026Published
- 16 Nov 2026First proof-of-concept repository on GitHub (unvetted)same day later
- 16 Nov 2026CISA SSVC assessment: exploitation none1 day later
- 16 Nov 2026CVE record last updatedsame day later
- 17 Nov 2026Analysed by vulneraibility.comsame day later
Common questions
Is CVE-2026-125423 being exploited?
Not confirmed. CVE-2026-125423 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-125423?
CVE-2026-125423 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-125423?
Yes. A fix has been recorded for CVE-2026-125423. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-125423 affect?
CVE-2026-125423 affects Gitea (self-hosted) < 28.4.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-125423?
Upgrade to Gitea v28.4.0+ immediately; restrict repo creation until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
5 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- github.com /go-gitea/gitea/security/advisories/GHSA-6m4f-m9vc-7946
Patches (2)
- github.com /go-gitea/gitea/pull/40376
- github.com /go-gitea/gitea/pull/40383
Other links (2)
- blog.gitea.com /release-of-28.4.0/
- github.com /go-gitea/gitea/releases/tag/v28.4.0
Also tracked as GHSA-6m4f-m9vc-7946 (OSV).
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- OSV: advisory aliases and downstream package versions
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.