Skip to main content

Janus Gateway EUVDEUVD-2026-97356

| CVE-2026-108831 LOW
Use of Hard-coded Credentials (CWE-798)
2026-10-12 VulDB GHSA-756g-w2hh-8pv3
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

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

  1. Access
    Reach exposed Janus demo pages
  2. Exploit
    Read hard-coded secret in admin.js
  3. Execution
    Authenticate to Admin API
  4. Impact
    Issue limited Admin API operations

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK

2 techniques across 2 tactics: Persistence, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the target deployment actually serves the bundled demo HTML/JavaScript (html/demos/admin.js) and exposes the Admin API reachable by the attacker - this is a demo/sample asset, not a core runtime path, so production deployments that do not ship the demo pages or that restrict Admin API access are not exposed. Per the CVSS 4.0 vector the issue is network-reachable (AV:N) with low complexity (AC:L) and requires low privileges (PR:L) with no user interaction (UI:N). Limiting factors: impact is bounded to Low confidentiality/integrity/availability with no subsequent-system scope change, affected versions are janus-gateway ≤ 1.4.2, and risk is confined to installations that have not removed or firewalled the demo content. Upgrading past 1.4.2 and not exposing demo pages removes the exposure.

Impact

This is a low-priority, low-real-risk issue despite being remotely reachable. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/PR:L/UI:N/VC:L/VI:L/VA:L) yields only a 2.1 score, with Low impact across confidentiality, integrity, and availability, and no subsequent-system impact (SC/SI/SA:N). The flaw is CWE-798 hard-coded credentials located in a client-side demo file (html/demos/admin.js) shipped with the Admin API component, not in the core gateway runtime - meaning the real exposure is limited to deployments that expose the bundled demo pages. The CVSS vector carries E:P (proof-of-concept) and the description states the exploit was publicly disclosed, so publicly available exploit code exists; however, there is NO CISA KEV listing and no EPSS value was provided in the input, so there is no evidence of widespread or active exploitation - this appears to be a disclosed-but-not-weaponized finding. A notable conflict: the single tag 'Authentication Bypass' overstates the issue, since CWE-798 (hard-coded credentials) is the documented weakness and the impacts are all rated Low, not a full authentication bypass granting elevated control. The sole source is VulDB with no vendor advisory, so affected-version and fix data are unverified.

Exploit ScenarioDerived

An attacker who can reach a Janus Gateway instance that serves the bundled HTML demo pages reads html/demos/admin.js, extracts the hard-coded credentials/secret embedded for the Admin API, and reuses them to authenticate to the Admin API. Public proof-of-concept disclosure means the credential location is already known; because the attack vector is network-based with low complexity, no local access or special tooling is required, though real impact is limited to the Low-rated confidentiality, integrity, and availability effects described.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 12, 2026

Hard-coded credentials in Meetecho Janus Gateway up to 1.4.2 can expose the Admin API through the bundled demo file html/demos/admin.js; the issue is remotely reachable and publicly available exploit code exists, but the independent assessment rates it low priority because exposure is limited to deployments that serve the demo content or leave the Admin API reachable. The CVSS 4.0 vector indicates low privileges (PR:L) with low confidentiality, integrity, and availability impact, and the provided references are VulDB entries rather than a confirmed vendor patch.

RemediationAI

No vendor-released patch identified at time of analysis, and the affected range is Meetecho Janus Gateway up to 1.4.2, so the intended remediation is to upgrade to a release after 1.4.2 once one is published. Until then, remove or block access to the bundled demo content, particularly html/demos/admin.js and the demo pages that load it, which prevents retrieval of the hard-coded credentials but may disable sample or documentation functionality. Restrict the Admin API to trusted networks, localhost, or a VPN and block its listener from untrusted sources; this limits exploitation but can interfere with remote administration workflows. If feasible, rotate or override the hard-coded credential in the deployment and never ship demo assets to production, while monitoring the VulDB references https://vuldb.com/vuln/416607 and https://vuldb.com/cve/CVE-2026-108831 for an official fix.

Affected VersionsENISA

janus-gateway 1.4.1
janus-gateway 1.4.0
janus-gateway 1.4.2

Affected Packages

euvd janus_gateway no fix

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

Janus Gateway is a WebRTC server whose Admin API provides management functions; this CWE-798 issue is a classic hard-coded credential exposure in client-side demo JavaScript rather than in the core gateway engine. The CPE cpe:2.3:a:meetecho:janus-gateway:*:*:*:*:*:*:*:* covers the affected Janus Gateway line through 1.4.2, and the vulnerable artifact is html/demos/admin.js. Because demo assets are sample code, the flaw is only reachable when a deployment actually serves those files and exposes the Admin API to the attacker's network; the CVSS 4.0 vector lists PR:L, while the independent CVSS 3.1 assessment scores PR:N, so authentication prerequisites are not fully consistent across sources and should be validated for the specific deployment.

Know when Janus Gateway 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 (VulDB) PRIMARY 2.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 7.3 HIGH

Hard-coded credentials require no prior access to use (PR:N) and the demo file is network-readable (AV:N/AC:L), but impact is confined to the limited Admin API demo context, so C/I/A are each Low.

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

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

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

Lifecycle Timeline

2
Severity Changed
Oct 12, 2026 - 13:22 NVD
MEDIUM LOW
CVSS changed
Oct 12, 2026 - 13:22 NVD
5.3 (MEDIUM) 2.1 (LOW)

DescriptionCVE.org

A security vulnerability has been detected in meetecho janus-gateway up to 1.4.2. This vulnerability affects unknown code of the file html/demos/admin.js of the component Admin API. Such manipulation leads to hard-coded credentials. The attack can be executed remotely. The exploit has been disclosed publicly and may be used.

Threat Intelligence Overview

EPSS Score
0.3%
Top 84% exploitable
Prevalence
Medium
popular open-source WebRTC gateway, niche beyond media/real-time deployments
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 LOW
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
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
Defer
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

10
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
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