# CVE-2026-127092: BuildAdmin 1.0.1 through 2.3.9 Stored XSS via X-Rewrite-URL in Admin Log


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-867h-r58x-95cx

## What is CVE-2026-127092?

CVE-2026-127092 is a medium-severity vulnerability in build-admin BuildAdmin, published on 13 Nov 2026. 

### Official description

BuildAdmin 1.0.1 through 2.3.9 contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to store javascript: URLs in the admin operation log via the X-Rewrite-URL header. When an administrator clicks the log entry's url open button, the script runs in the backend origin and steals the adminInfo token from localStorage, enabling account takeover.

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

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

1 open source package ship an affected version, including build-admin/buildadmin.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `build-admin/buildadmin` | GitHub | `pkg:github/build-admin/buildadmin` | From 1.0.1 to 2.3.9 | None |

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

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

## Is CVE-2026-127092 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127092 is a medium-severity vulnerability in build-admin BuildAdmin, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-127092 exists.

Affected packages and fixed versions:
- build-admin/buildadmin (GitHub): affected from 1.0.1 up to 2.3.9; no fix listed

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

## Sources

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

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