dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 2 Feb 2026.
GogsApplication

CVE-2025-8110

HIGH · 8.8 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to after 0.13.3 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable Zero-click Patch available

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
Improper Symbolic link handling in the PutContents API in Gogs allows Local Execution of Code.

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 · high confidence

Gogs contains a symlink handling vulnerability in its PutContents API where improper validation of symbolic links allows an attacker to write files outside the intended repository directory, leading to local code execution on the host system.

MitigationUpgrade Gogs to the patched version that properly validates symlink targets within the PutContents API. If patching is not immediately feasible, restrict write access to the API and monitor for suspicious symlink creation patterns.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GogsApplication
Affected:<= 0.13.3

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify the installed Gogs version
    Access the Gogs admin panel or check the binary/file version. On Linux, you can run `gogs --version` or check the binary metadata. Also check the /about page in the web interface which often displays the version.
    Affected if The installed version is 0.13.3 or any earlier version (anything <= 0.13.3).
  2. Verify user authentication is enabled
    Check the Gogs configuration file (usually app.ini) for the [service] section and ensure DISABLE_REGISTER or REQUIRE_SIGNIN_VIEW is not set to allow unauthenticated access. The vulnerability requires an authenticated user.
    Affected if Anonymous/unauthenticated access to the PutContents API is possible, the vulnerability can be exploited by any user with repository access.
  3. Confirm PutContents API is accessible
    Attempt to access the Gogs API endpoint for PutContents (typically /api/v1/repos/{owner}/{repo}/contents/{path}) using a valid authenticated session or API token.
    Affected if The API endpoint responds successfully to authenticated requests, indicating the feature is enabled and exploitable.
  4. Check if repositories allow symbolic link creation
    Create a test repository and attempt to create a symbolic link within it using the Gogs web interface or API. Verify that symbolic links can be committed to the repository.
    Affected if Symbolic links can be created and committed to repositories, which is the mechanism used for the path traversal attack.

You are affected if Gogs version is 0.13.3 or earlier AND authenticated users can access the PutContents API AND symbolic links can be created in repositories.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.13.3
Vendor patch github.com →
Interim mitigation

Upgrade Gogs to the patched version that properly validates symlink targets within the PutContents API. If patching is not immediately feasible, restrict write access to the API and monitor for suspicious symlink creation patterns.

Recommended fix Moderate confidence

Gogs version 0.13.4 or later

  1. 1. Backup your current Gogs installation and data directory
  2. 2. Stop the Gogs service
  3. 3. Download the latest Gogs release (version 0.13.4 or later) from the official repository
  4. 4. Replace the existing Gogs binary with the new version
  5. 5. Restart the Gogs service
  6. 6. Verify the installation by checking the Gogs web interface and testing repository operations
Caveat Review release notes for any configuration or feature changes between your current version and the upgrade target

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gogs Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8110 — 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-2025-8110 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