# CVE-2026-116747: Kener 3.0.0 before 4.1.10 Authentication Bypass via Hardcoded Fallback JWT Secret


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-7973-f655-53vh

## What is CVE-2026-116747?

CVE-2026-116747 is a critical vulnerability in rajnandan1 kener, published on 26 Oct 2026. 

### Official description

Kener 3.0.0 before 4.1.10 contains an authentication bypass vulnerability that allows unauthenticated attackers to forge session tokens by using the hardcoded DUMMY_SECRET fallback key. When KENER_SECRET_KEY is empty or unset, attackers knowing an administrator email can sign a kener-user cookie to access /manage/api with full administrative privileges or forge password-reset tokens.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2026-116747 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116747 is a critical vulnerability in rajnandan1 kener, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116747 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-116747/ (Markdown: https://insights.sbomify.com/CVE-2026-116747/index.md)
```

## Sources

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

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