Skip to main content

Kener CVE-2026-116747

| EUVDEUVD-2026-110495 CRITICAL
Use of Hard-coded Cryptographic Key (CWE-321)
2026-10-26 VulnCheck GHSA-7973-f655-53vh
9.2
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify Kener instance with unset KENER_SECRET_KEY
  2. Delivery
    Obtain an administrator email address
  3. Exploit
    Forge kener-user JWT signed with DUMMY_SECRET
  4. Execution
    Submit forged cookie to /manage/api
  5. Impact
    Gain full administrative control or reset admin password

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
Exploitation Conditions

The decisive prerequisite is that the target Kener instance runs with the KENER_SECRET_KEY environment variable empty or unset, which activates the hardcoded 'DUMMY_SECRET' fallback used to sign and verify the kener-user JWT session cookie, password-reset tokens, and API-key HMACs. The attacker must also know (or correctly guess) an administrator's email address to populate the forged token's claims. The vulnerability affects Kener 3.0.0 through versions before 4.1.10. Principal limiting factor: any instance that has set a strong, unique KENER_SECRET_KEY is not exploitable, because the forged token will fail verification against the real key - this is the AT:P attack requirement in the 4.0 vector. No user interaction and no authentication are required against a misconfigured instance (PR:N/UI:N), and the admin management surface is reached over the network (/manage/api).

Impact

Signals conflict in an instructive way. The CVSS 4.0 base score is 9.2 (critical) with AV:N/AC:L/PR:N/UI:N and full VC:H/VI:H/VA:H impact, and the vuln.today decision label is act_now, which argues for urgent remediation. However, the 4.0 vector itself carries AT:P (an attack requirement), reflecting that exploitation is gated on a specific condition: the instance must be running with KENER_SECRET_KEY empty or unset so the hardcoded DUMMY_SECRET fallback is active. EPSS is only 0.62% (50th percentile), i.e. middling-to-low predicted exploitation, and the CVE is NOT in CISA KEV, so there is no confirmed active exploitation. There is no public exploit identified at time of analysis, though the vendor patch (and its regression test) openly demonstrates the forging technique (jwt.sign of an admin claim with 'DUMMY_SECRET'), making the mechanism trivially reconstructible for any attacker who reads the fix. Net: for instances actually left on the fallback secret this is a genuine, high-priority unauthenticated full-admin compromise and the act_now label is justified; for correctly configured instances (a strong KENER_SECRET_KEY set) it is not exploitable at all. The low EPSS likely reflects both the small deployment footprint and the configuration dependency rather than low impact.

Exploit ScenarioDerived

An attacker locates an internet-exposed Kener instance (versions 3.0.0 up to but not including 4.1.10) that is running with KENER_SECRET_KEY empty or unset, so the DUMMY_SECRET fallback is in use. Knowing or guessing an administrator's email, the attacker signs a kener-user JWT cookie with 'DUMMY_SECRET' and presents it to /manage/api to obtain full administrative privileges, or forges a password-reset token for that account. No public exploit is identified at time of analysis, but the vendor's own patch test shows the one-line forging method, so the barrier to reproduction is minimal given AV:N/AC:L.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 28, 2026

Authentication bypass in Kener 3.0.0 through 4.1.9 lets unauthenticated remote attackers who know an administrator's email address forge a kener-user JWT session cookie and reach /manage/api with full administrative privileges, and also forge password-reset tokens, because the application silently falls back to the hardcoded string 'DUMMY_SECRET' when KENER_SECRET_KEY is empty or unset. The flaw is conditional rather than universal: the assessed vector is AC:H/AT:P precisely because any instance configured with a strong, unique KENER_SECRET_KEY rejects the forged token, so only default or misconfigured deployments are exploitable - but those deployments are fully compromised with no credentials and no user interaction. No public exploit code is confirmed at time of analysis and there is no KEV listing; EPSS is 0.62% (50th percentile), which understates the risk for unhardened instances, and the vendor priority label is act_now.

RemediationAI

Upgrade to Kener 4.1.10 or later; the tagged release is at https://github.com/rajnandan1/kener/releases/tag/v4.1.10 and the fix commit is ff636483544c926eab5b5e3e26b811c0f52bcaf8, with the vendor advisory at https://www.vulncheck.com/advisories/kener-3.0.0-before-4.1.10-authentication-bypass-via-hardcoded-fallback-jwt-secret. If upgrading immediately is not possible, the effective workaround is to define KENER_SECRET_KEY to a long random value (for example the output of openssl rand -base64 32) so that the DUMMY_SECRET fallback is never used; do this before exposing the instance, and never leave the variable empty or set it to a published example value such as 'DUMMY_SECRET', 'replace_me_with_a_random_string', 'some_secret_key_for_kener' or 'your-super-secret-key-here', all of which the fixed code explicitly warns about. Be aware of the trade-off: rotating KENER_SECRET_KEY invalidates every existing session and every existing API key, forcing administrators to sign in again and re-issue API keys, so schedule the change. In 4.1.10 and later an unset key is fail-closed - sign-in, password reset and API-key functions stay disabled until the variable is set - which is the intended safe failure mode but will lock out administrators who deploy without setting it. Restricting network access to /manage/api at a reverse proxy or firewall limits exposure during the upgrade window, at the cost of blocking legitimate administrative access from outside the trusted network.

Affected VersionsENISA

kener 3.0.0 <4.1.10

Affected Packages

euvd kener fix: 4.1.10

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Kener is a Node/TypeScript self-hosted status-page application that authenticates administrators with JSON Web Tokens issued through the jsonwebtoken library and stored in a kener-user cookie; the same secret is reused to sign password-reset tokens and to derive HMAC-SHA256 hashes of API keys. The root cause is CWE-321, use of a hardcoded cryptographic key: the signing and verification helpers in src/lib/server/controllers/commonController.ts resolved the key as process.env.KENER_SECRET_KEY || DUMMY_SECRET, so an unset or empty environment variable did not fail closed but instead produced a globally known HMAC secret that is visible in the public source. An attacker who knows an administrator's email can therefore mint a token with that email in the claims and have it accepted by the manage API, or mint a reset token. Impact is confined to confidentiality, integrity and availability of the Kener instance (S:U in the assessed vector) - there is no scope escape into the host or other systems described. The upstream fix removes the literal entirely: a GetSecretKey() helper throws when the variable is absent, verification never falls back, and a SecretKeyWarning() helper flags published example values such as 'DUMMY_SECRET', 'replace_me_with_a_random_string' and 'some_secret_key_for_kener'. Accompanying tests confirm forged tokens signed with DUMMY_SECRET are rejected and that an unset key blocks token generation, hashing and sign-in.

Know when Kener gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 9.2 CRITICAL
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
vuln.today AI 8.1 HIGH

Unauthenticated network attack (PR:N/UI:N) yielding full admin, but gated on the instance running with an empty/unset secret key and knowledge of an admin email, a condition outside attacker control, so AC:H.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A critical authentication bypass in Kener (versions 3.0.0 through 4.1.9) allows attackers to gain full administrative control of unprotected instances if they know an administrator's email. This affects organizations running default or misconfigured deployments, where a missing secret key renders them immediately exploitable without any user interaction, enabling data theft, service disruption, and reputational harm.

Business Impact: High
Compensating Controls

Apply vendor patch. Until patching is complete, ensure KENER_SECRET_KEY is set to a strong, unique value (not empty or 'DUMMY_SECRET') and restrict network access to Kener management interfaces to trusted users only.

Threat Intelligence Overview

EPSS Score
0.6%
Top 50% exploitable
Prevalence
Low
niche self-hosted open-source status-page / uptime-monitor tool
Social Media
2
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy