CVE-2026-22547
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 · uneditedGitea versions before 1.25.5 lack validation constraints for repository creation fields, including length-limited template fields and trust model or object format values.
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 confidenceGitea before version 1.25.5 does not enforce validation constraints on repository creation fields, allowing oversized or malformed input for template fields (missing length limits), trust model values, and object format values. This missing input validation could enable injection attacks or denial-of-service conditions via specially crafted repository creation requests.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Gitea versionRun 'gitea --version' or check the Gitea admin dashboard version display to determine the currently running versionAffected if The version number is lower than 1.25.5 (for example 1.25.0, 1.24.x, or earlier)
-
Confirm repository creation is enabledVerify that the Gitea instance allows repository creation by users - check admin settings or the ability to access the 'New Repository' page via web UI or API endpoint '/repo/create'Affected if Repository creation functionality is active and accessible to users or external clients
-
Identify if self-hosted or managed serviceDetermine whether you are running Gitea self-hosted (installed via binary, Docker, or package) or using a managed Gitea hosting serviceAffected if Running a self-hosted instance where you control the Gitea version, the version check in step 1 determines exposure; for managed services, contact the provider for version information
You are affected if your Gitea version is before 1.25.5 AND repository creation is enabled and accessible to potentially untrusted users or external callers.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade Gitea to version 1.25.5 or later which implements proper validation constraints for repository creation fields including length limits, trust model validation, and object format verification.
1.25.5
- Upgrade Gitea to version 1.25.5 or later to resolve the improper input validation vulnerability
- After upgrading, verify that repository creation fields now enforce validation constraints for length-limited template fields, trust model values, and object format values
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22547 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22547 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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