# CVE-2026-92140: Cross-site scripting in Jenkins Gitee Plugin

> Attackers can inject malicious scripts via Gitee webhook payloads, leading to stored XSS in Jenkins build causes.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-3h9w-3jjf-qw2v

## What is CVE-2026-92140?

CVE-2026-92140 is a medium-severity cross-site scripting vulnerability in Jenkins Gitee Plugin, published on 16 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Jenkins Gitee Plugin 1301.v8957053c7902 and earlier does not escape the sender name from Gitee push webhook payloads in build causes, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to trigger builds via the Jenkins Gitee Plugin webhook endpoint.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-92140?


## How do I fix CVE-2026-92140?

No fix has been published for CVE-2026-92140 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92140 being exploited?

There is no known exploitation of CVE-2026-92140 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92140 and fix it if it is affected.

What it is: CVE-2026-92140 is a medium-severity cross-site scripting vulnerability in Jenkins Gitee Plugin, published on 16 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92140 in the wild and no public exploit code.

Affected product: Jenkins Gitee Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92140/ (Markdown: https://insights.sbomify.com/CVE-2026-92140/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92140
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92140
- OSV: https://osv.dev/vulnerability/CVE-2026-92140

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92140/
Summaries are generated and may contain mistakes; the official description above is the record.