# CVE-2026-105030: Kener 4.0.0 before 4.1.6 Hidden Monitor Data Disclosure via Dashboard API

> Unauthenticated attackers can retrieve hidden monitor data via dashboard API endpoints lacking visibility filters, exposing sensitive status information.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-9wr3-32qm-xqr7

## What is CVE-2026-105030?

CVE-2026-105030 is a medium-severity vulnerability in rajnandan1 kener, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kener 4.0.0 before 4.1.6 contains an information disclosure vulnerability that allows unauthenticated attackers to retrieve hidden or inactive monitor data by querying dashboard API handlers lacking visibility filters. Attackers can supply a known or guessed monitor tag to endpoints such as monitor-bar and monitor-latency-chart to obtain names, descriptions, status, uptime history and latency.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-105030 being exploited?

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

Public exploit code:

- A python3 PoC for CVE-2026-105030 Kener 4.0.0 before 4.1.6 Hidden Monitor Data Disclosure via Dashboard API (github_poc): https://github.com/asvorg/CVE-2026-105030-poc

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105030 is a medium-severity vulnerability in rajnandan1 kener, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105030 in the wild and no public exploit code.

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

## Sources

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

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