dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-22874

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-03
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Gitea versions up to and including 1.26.2 have incomplete SSRF protection in webhook and migration allow-list filtering.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Gitea versions up to 1.26.2 contain an incomplete SSRF (Server-Side Request Forgery) protection mechanism in webhook and migration allow-list filtering. The vulnerability allows attackers to potentially make the Gitea server request internal resources or bypass intended network restrictions through webhook and migration features.

MitigationRestrict webhook and migration endpoints to only permit external, publicly reachable URLs by implementing stricter allow-list validation that blocks internal IP ranges, localhost, and private network addresses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Gitea version
    Run 'gitea --version' from the Gitea binary, or check the version displayed in the Gitea admin dashboard under 'Site Administration' > 'System Info'. Alternatively, inspect the version string in the gitea binary file if CLI access is unavailable.
    Affected if The installed version is 1.26.2 or any earlier version (e.g., 1.26.0, 1.25.x, etc.). This vulnerability affects all versions up to and including 1.26.2.
  2. Verify webhook functionality is accessible
    Confirm that the Gitea web interface allows access to webhook configuration. This is typically available at '/repo/settings/hooks' for repository webhooks and '/admin/webhooks' for system webhooks. Check if the webhook creation or editing interface is reachable.
    Affected if Webhooks are enabled and accessible to users (this is the default state in Gitea). The vulnerability exists in the webhook allow-list filtering mechanism.
  3. Verify migration functionality is accessible
    Confirm that migration features are available. This includes the ability to migrate repositories from external sources, typically accessible via 'New Migration' option or '/repo/migrate'. Check if migration import forms are reachable.
    Affected if Migration features are enabled and accessible (this is the default state in Gitea). The vulnerability exists in the migration allow-list filtering mechanism.
  4. Inspect webhook allow-list configuration
    Review the Gitea configuration file (app.ini) for any custom webhook URL allow-list settings. Look for sections related to webhooks or webhook validation. Check if internal IPs, localhost, or private ranges are explicitly blocked in the configuration.
    Affected if The webhook allow-list either lacks explicit blocking of internal/private IP ranges (127.0.0.1, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, etc.) or uses an incomplete filtering mechanism.
  5. Inspect migration allow-list configuration
    Review the Gitea configuration file (app.ini) for migration-related settings. Look for allow-list or whitelist configurations related to repository migrations. Check if internal URLs and private network addresses are explicitly denied.
    Affected if The migration allow-list either lacks explicit blocking of internal/private URLs or implements incomplete filtering that could allow internal resource access.

You are affected if your Gitea version is 1.26.2 or earlier AND webhook and/or migration features are accessible, as the incomplete SSRF protection in their allow-list filtering could allow attackers to access internal resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Restrict webhook and migration endpoints to only permit external, publicly reachable URLs by implementing stricter allow-list validation that blocks internal IP ranges, localhost, and private network addresses.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22874 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data