CVE-2026-120729 (GCVE-0-2026-120729)

Vulnerability from cvelistv5 – Published: 2026-11-15 21:13 – Updated: 2026-11-15 21:13
VLAI
Title
Gitea stored cross-site scripting in the issue reference popup
Summary
The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of the response as HTML. A user who can post a comment or other rendered content could add a link that is displayed as an ordinary issue reference but points to a file in a repository they control, so that the popup inserted that file's content into the page of anyone hovering the link and ran script in the viewer's session. The popup now requests the issue by the owner, repository and index parsed from the link.
Severity
No CVSS data available.
CWE
  • CWE-79 - Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Assigner
Gitea CNA under the mitre root
CNA scorecard C 61/100 over 205 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Gitea Gitea Affected: 1.27.0 , < 28.4.0 (semver)
guessed Create a notification for this product.
Credits
https://github.com/silverwind
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageName": "gitea.dev",
          "product": "Gitea",
          "vendor": "Gitea",
          "versions": [
            {
              "lessThan": "28.4.0",
              "status": "affected",
              "version": "1.27.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "https://github.com/silverwind"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of the response as HTML. A user who can post a comment or other rendered content could add a link that is displayed as an ordinary issue reference but points to a file in a repository they control, so that the popup inserted that file\u0027s content into the page of anyone hovering the link and ran script in the viewer\u0027s session. The popup now requests the issue by the owner, repository and index parsed from the link."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-79",
              "description": "CWE-79: Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-15T21:13:53.375Z",
        "orgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
        "shortName": "Gitea"
      },
      "references": [
        {
          "name": "GitHub Security Advisory GHSA-wmr3-xg9x-vc55",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-wmr3-xg9x-vc55"
        },
        {
          "name": "Fix: go-gitea/gitea pull request #40207",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/go-gitea/gitea/pull/40207"
        },
        {
          "name": "Fix backport to release/v28: go-gitea/gitea pull request #40225",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/go-gitea/gitea/pull/40225"
        },
        {
          "name": "Gitea 28.4.0 release announcement",
          "tags": [
            "release-notes"
          ],
          "url": "https://blog.gitea.com/release-of-28.4.0/"
        },
        {
          "name": "go-gitea/gitea v28.4.0 release",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/go-gitea/gitea/releases/tag/v28.4.0"
        }
      ],
      "title": "Gitea stored cross-site scripting in the issue reference popup"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
    "assignerShortName": "Gitea",
    "cveId": "CVE-2026-120729",
    "datePublished": "2026-11-15T21:13:53.375Z",
    "dateReserved": "2026-11-15T20:29:37.625Z",
    "dateUpdated": "2026-11-15T21:13:53.375Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "packageName": "gitea.dev",
                "product": "Gitea",
                "vendor": "Gitea",
                "versions": [
                  {
                    "lessThan": "28.4.0",
                    "status": "affected",
                    "version": "1.27.0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of the response as HTML. A user who can post a comment or other rendered content could add a link that is displayed as an ordinary issue reference but points to a file in a repository they control, so that the popup inserted that file\u0027s content into the page of anyone hovering the link and ran script in the viewer\u0027s session. The popup now requests the issue by the owner, repository and index parsed from the link."
          }
        ],
        "id": "CVE-2026-120729",
        "lastModified": "2026-11-15T22:17:17.870",
        "metrics": {},
        "published": "2026-11-15T22:17:17.773",
        "references": [
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://blog.gitea.com/release-of-28.4.0/"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/pull/40207"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/pull/40225"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/releases/tag/v28.4.0"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-wmr3-xg9x-vc55"
          }
        ],
        "sourceIdentifier": "88ee5874-cf24-4952-aea0-31affedb7ff2",
        "vulnStatus": "Deferred",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-79"
              }
            ],
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "type": "Secondary"
          }
        ]
      }
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.