CVE-2026-67444knrdl hubleys-dashboard cross-site scripting
CVE-2026-67444 is a cross-site scripting in knrdl hubleys-dashboard, rated high (7.1 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
Input is written into a web page without escaping, so an attacker's script runs in the browser of anyone who views it. Files of dangerous types can be uploaded, and the server may run or serve them.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
A successful attack can change data or behaviour. In practice, this kind of flaw lets an attacker act inside a signed-in user's browser session.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade knrdl hubleys-dashboard to 0.5.2 or later.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
Hubleys is a dashboard for self-hosted services. Prior to version 0.5.2, any authenticated (non-admin) Hubleys user can upload a file with an arbitrary extension as their dashboard "background image," and the server will later serve that file back with a Content-Type derived straight from the attacker's chosen extension - so uploading an .html file gets it served as text/html. Because the endpoint that serves it returns a manually-constructed response rather than going through SvelteKit's normal page-rendering pipeline, the app's configured Content-Security-Policy never gets attached to it either, so a script embedded in the upload runs unrestricted. This issue has been patched in version 0.5.2.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Web front ends and single-page apps. The flaw sits between a user's browser and the web application.
- Admin consoles served to a browser. The flaw sits between a user's browser and the web application.
- Upload endpoints and the storage behind them. The flaw sits between uploaded content and the servers that store or serve it.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between a user's browser and the web application. An attacker who crosses it can act inside a signed-in user's browser session.
- Between uploaded content and the servers that store or serve it. An attacker who crosses it can place a file the server will run or serve to others.
Questions to answer about your own systems
- Where does knrdl hubleys-dashboard run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.