# CVE-2026-130841: ioBroker.lovelace before 7.0.0 Unauthenticated Path Traversal via cards Route


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-mc3g-g473-hf5w

## What is CVE-2026-130841?

CVE-2026-130841 is a high-severity vulnerability in ioBroker.lovelace, published on 17 Nov 2026. 

### Official description

ioBroker.lovelace before 7.0.0 contains a path traversal vulnerability in the onCards() request handler that allows unauthenticated remote attackers to read arbitrary files via unsanitized dot-dot segments. Attackers can send crafted requests to the /cards/_static_/, /hacsfiles/, or /local/custom_ui/ routes to read files including ioBroker configuration and stored credentials.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

1 open source package ship an affected version, including iobroker.lovelace.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `iobroker.lovelace` | npm | `pkg:npm/iobroker.lovelace` | All versions | 7.0.0 |

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

Upgrade iobroker.lovelace to 7.0.0 or later.

## Is CVE-2026-130841 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130841 is a high-severity vulnerability in ioBroker.lovelace, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130841 in the wild and no public exploit code.

Affected packages and fixed versions:
- iobroker.lovelace (npm): affected all versions; fixed in 7.0.0

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

## Sources

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

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