# CVE-2026-59102: Forgejo < 15.0.3 - Stored XSS via Actions Run Full Name Rendering

> Authenticated attackers can execute arbitrary JavaScript in other users' browsers via stored XSS in Actions run full names when specific display options are enabled.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-r26p-rw8p-x468

## What is CVE-2026-59102?

CVE-2026-59102 is a low-severity cross-site scripting vulnerability in forgejo, published on 2 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Forgejo before 15.0.3 contains a stored cross-site scripting vulnerability that allows authenticated attackers to execute arbitrary JavaScript in other users' browsers by setting a full name containing an HTML payload and triggering an Actions run. When the DEFAULT_SHOW_FULL_NAME option is enabled, the run description is assembled server-side with the user's display name interpolated into an HTML string via a translation function that does not escape its arguments, and the frontend renders the result using a Vue v-html binding, causing script execution for any user who views the affected Actions run page.

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

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


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

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

## Is CVE-2026-59102 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59102 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59102 is a low-severity cross-site scripting vulnerability in forgejo, published on 2 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59102 exists.

Affected product: forgejo. 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-59102/ (Markdown: https://insights.sbomify.com/CVE-2026-59102/index.md)
```

## Sources

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

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