PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-25718 Gitea CVE debrief

Gitea versions before 1.25.5 have a vulnerability in path resolution during template repository generation. This allows template processing to read or write through symlinked or otherwise non-regular paths. The vulnerability has a CVSS score of 9.1 and is considered CRITICAL. Users of Gitea versions before 1.25.5 should review and apply patches to prevent potential path resolution issues during template repository generation. The CVE record was published on 2026-07-03T21:16:57.823Z and has not been modified since then.

Vendor
Gitea
Product
Gitea Open Source Git Server
CVSS
CRITICAL 9.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-03
Original CVE updated
2026-07-07
Advisory published
2026-07-03
Advisory updated
2026-07-07

Who should care

Users of Gitea versions before 1.25.5 should review and apply patches to prevent potential path resolution issues during template repository generation. Affected operator, platform, vulnerability-management, and security-team impact should be considered. Defenders should verify the scope of the vulnerability and apply patches or mitigations as needed.

Technical summary

Gitea versions before 1.25.5 have a vulnerability in path resolution during template repository generation. This allows template processing to read or write through symlinked or otherwise non-regular paths. The vulnerability has a CVSS score of 9.1 and is considered CRITICAL. Affected product deployments should be reviewed for potential exposure. Defenders should verify the scope of the vulnerability and apply patches or mitigations as needed.

Defensive priority

High priority should be given to updating Gitea to version 1.25.5 or later to address the path resolution vulnerability.

Recommended defensive actions

  • Update Gitea to version 1.25.5 or later
  • Review template repository generation configurations
  • Monitor for suspicious template processing activity
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

Evidence is based on limited source detail from the NVD and Gitea release notes. Further verification is recommended. The CVE record was published on 2026-07-03T21:16:57.823Z and has not been modified since then. Affected product deployments should be reviewed for potential exposure. Defenders should verify the scope of the vulnerability and apply patches or mitigations as needed.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-25718 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-25718

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-25718 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-25718

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://blog.gitea.com/release-of-1.25.5/

    88ee5874-cf24-4952-aea0-31affedb7ff2

  • Source reference

    Unverified legacy reference

    URL: https://github.com/go-gitea/gitea/pull/36734

    88ee5874-cf24-4952-aea0-31affedb7ff2

  • Source reference

    Unverified legacy reference

    URL: https://github.com/go-gitea/gitea/pull/36746

    88ee5874-cf24-4952-aea0-31affedb7ff2

  • Source reference

    Unverified legacy reference

    URL: https://github.com/go-gitea/gitea/releases/tag/v1.25.5

    88ee5874-cf24-4952-aea0-31affedb7ff2

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.