HighCVE-2026-73800

    Gitea: Improper Control of Generation of Code ('Code Injection') (CVE-2026-73800)

    Published Sources: BSI

    Share

    What is affected, what to do

    Gitea resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event. A fork author can modify a referenced reusable workflow so attacker-controlled code executes with the repository and organization secrets available to that event.

    Update Gitea to version 1.27.2.

    Affected
    • Gitea lt 1.19.0..1.27.2
    Fixed in
    • Gitea 1.27.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: BSI

    0.5 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 45.2

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    83.52 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.5 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    45.2
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 18 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-94, CWE-829

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Gitea resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event. A fork author can modify a referenced reusable workflow so attacker-controlled code executes with the repository and organization secrets available to that event. Exploitation requires a base workflow that calls a local reusable workflow, and bypasses the intended separation between trusted base code and untrusted fork code.

    Source: BSI WID Portal

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    GiteaGitea
    • 1.16.0 – ≤ 1.27.1
    • 1.19.0 – < 1.27.2
    • 1.27.0 – ≤ 1.27.1
    • ≤ 1.26.4
    • ≤ 1.27.1
    • —
    • 1.27.2
    • —
    • —
    • —
    giteagitea
    • 1.16.0 – < 1.27.2
    • 1.27.2
    Open SourceGitea
    • < 1.27.2
    • 1.27.2
    Distribution and container packages (1)

    Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.

    Distribution and container packages
    Affected versionsFixed in
    bitnamigitea
    • 1.16.0
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-94Improper Control of Generation of Code ('Code Injection')

      Base

      The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

      Entry at MITRE CWE-94

    • CWE-829Inclusion of Functionality from Untrusted Control Sphere

      Base

      The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.

      Entry at MITRE CWE-829

    References & sources

    • github.comGitHub Security Advisory GHSA-q55v-4cmj-xh65Vendor advisory
    • blog.gitea.comGitea 1.27.2 release announcementRelease notes
    • github.comFix: go-gitea/gitea pull request #38862Patch
    • github.comFix: go-gitea/gitea pull request #38895Patch
    • github.comgo-gitea/gitea v1.27.2 releaseRelease notes
    • github.comGitHub Security Advisory GHSA-7452-653r-6gp8Vendor advisory
    • github.comFix: go-gitea/gitea pull request #38793Patch
    • github.comFix: go-gitea/gitea pull request #38795Patch
    • github.comGitHub Security Advisory GHSA-r9ch-mqjm-g67vVendor advisory
    • github.comFix: go-gitea/gitea pull request #38886Patch
    • github.comFix: go-gitea/gitea pull request #38897Patch
    • github.comGitHub Security Advisory GHSA-92j2-6qcg-c28cVendor advisory
    • github.comFix: go-gitea/gitea pull request #38805Patch
    • github.comFix: go-gitea/gitea pull request #38810Patch
    • NVD (NIST)vuln/detail/CVE-2026-73278web
    • github.comGitHub Security Advisory GHSA-579w-82gf-89m2Vendor advisory
    • github.comFix: go-gitea/gitea pull request #38885Patch
    • github.comFix: go-gitea/gitea pull request #38898Patch
    • github.comGitHub Security Advisory GHSA-8xjr-x7rg-hp5hVendor advisory
    • github.comGitHub Security Advisory GHSA-h62v-wmrr-5qjqVendor advisory

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. ReceivedGitea

      Weakness type: CWE-94, CWE-829

      Description added or changed

      Show 9 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      Gitea resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event. A fork author can modify a referenced reusable workflow so attacker-controlled code executes with the repository and organization secrets available to that event. Exploitation requires a base workflow that calls a local reusable workflow, and bypasses the intended separation between trusted base code and untrusted fork code.
      Weakness type (CWE)added
      —
      CWE-94
      Weakness type (CWE)added
      —
      CWE-829
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/73xxx/CVE-2026-73800.json">CVE-2026-73800</a>
      Referenceadded
      —
      https://blog.gitea.com/release-of-1.27.2/
      Referenceadded
      —
      https://github.com/go-gitea/gitea/pull/38886
      Referenceadded
      —
      https://github.com/go-gitea/gitea/pull/38897
      Referenceadded
      —
      https://github.com/go-gitea/gitea/releases/tag/v1.27.2
      Referenceadded
      —
      https://github.com/go-gitea/gitea/security/advisories/GHSA-r9ch-mqjm-g67v

      Source identifier: 88ee5874-cf24-4952-aea0-31affedb7ff2

    Linked CVEs

    Linked CVEs
    MediumCVE-2026-73814Gitea repository ownership escalation by administrators6.5—
    HighCVE-2026-73804Gitea API token scope escalation through HTTP signatures8.1—
    HighCVE-2026-73800Gitea reusable workflow secret exposure in pull_request_target8.8—
    HighCVE-2026-73539Gitea external renderer argument injection and code execution7.5—
    HighCVE-2026-73535Gitea second-factor bypass through OpenID identity linking8.8—
    CriticalCVE-2026-73278Gitea WebAuthn bypass during OAuth and OIDC sign-in9.8—
    LowCVE-2026-60008Gitea Jupyter notebook UI redress through CSS class injection3.5—
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-73800
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-73800"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-73800.svg?lang=en" alt="CVE-2026-73800 – NEOSEC Intel" height="20"></a>