# CVE-2026-33510: DOM-Based XSS in Homarr /auth/login Redirect

> An attacker can execute arbitrary JavaScript in an authenticated user's browser via a malicious link, potentially stealing credentials or performing unauthorized actions.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-79pg-554g-rw82

## What is CVE-2026-33510?

CVE-2026-33510 is a high-severity cross-site scripting vulnerability in homarr-labs homarr, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Homarr is an open-source dashboard. Prior to 1.57.0, a DOM-based Cross-Site Scripting (XSS) vulnerability has been discovered in Homarr's /auth/login page. The application improperly trusts a URL parameter (callbackUrl), which is passed to redirect and router.push. An attacker can craft a malicious link that, when opened by an authenticated user, performs a client-side redirect and executes arbitrary JavaScript in the context of their browser. This could lead to credential theft, internal network pivoting, and unauthorized actions performed on behalf of the victim. This vulnerability is fixed in 1.57.0.

Weakness: CWE-87 (Improper Neutralization of Alternate XSS Syntax), CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Homarr Homarr.

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

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

## Is CVE-2026-33510 being exploited?

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

## Other vulnerabilities in homarr-labs homarr

- [CVE-2025-64759](https://insights.sbomify.com/CVE-2025-64759/): Homarr is Vulnerable to Stored Cross-Site Scripting (XSS) and Possible Privilege Escalation via Malicious SVG Upload (high 8.1)
- [CVE-2025-67493](https://insights.sbomify.com/CVE-2025-67493/): Homarr: missing input sanitization and possible privilege escalation through ldap search query injection (high 7.5)
- [CVE-2026-27796](https://insights.sbomify.com/CVE-2026-27796/): Homarr: Unauthenticated Information Disclosure (Integration Metadata Leak) (medium 5.3)
- [CVE-2026-27797](https://insights.sbomify.com/CVE-2026-27797/): Homarr: Unauthenticated SSRF in rssFeed.ts (medium 5.3)
- [CVE-2026-25123](https://insights.sbomify.com/CVE-2026-25123/): Homarr affected by Unauthenticated SSRF / Port-Scan Primitive via widget.app.ping (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33510 is a high-severity cross-site scripting vulnerability in homarr-labs homarr, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, 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-33510 exists.

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

## Sources

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

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