CVE-2026-0622

Open 5GS WebUI uses a hard-coded JWT signing key

Published Jan 20, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
Open 5GS WebUI uses a hard-coded JWT signing key (change-me) whenever the environment variable JWT_SECRET_KEY is unset

Analysis

AI-generated

Technical impact

The vulnerability lies in the Open 5GS WebUI component that falls back to a hard‑coded JWT signing key (“change‑me”) when the environment variable JWT_SECRET_KEY is not set. This flaw allows an attacker to forge valid JSON Web Tokens without needing valid credentials. The attacker can then authenticate as the WebUI administrator and read, modify, or delete network configuration and subscriber data. The weakness is identified as CWE‑798: Hard‑coded cryptographic key, and the impact is a loss of authentication integrity, potentially leading to full control over the 5G core network.

Affected Systems

Affected systems include the Open 5GS WebUI service provided by NewPlane:open5GS. Any deployment of open5GS that does not explicitly define JWT_SECRET_KEY at launch is susceptible. Version information is not specified in the advisory, implying all current releases that use the default hard‑coded key are at risk.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity, and the EPSS score of less than 1% suggests a low current probability of exploitation in the wild. The vulnerability is not listed in CISA’s KEV catalog. Exploitation is straightforward: an attacker with network access to the WebUI can construct a JWT signed with the known key and gain administrator privileges without needing to bypass any other authentication mechanism. Because the flaw resides in the default key logic, it can be triggered immediately without additional configuration changes on the target system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Set the JWT_SECRET_KEY environment variable to a strong, unique key before starting the open5GS WebUI service to prevent the hard‑coded key from being used
  • Apply the latest kernel or Open 5GS patch that removes the hard‑coded JWT secret key and implements secure key management
  • Restart the Open 5GS WebUI service after applying the variable change or patch to ensure the new configuration takes effect

Generated by OpenCVE AI on April 18, 2026 at 04:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-798
CPEs cpe:2.3:a:open5gs:open5gs:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Open5gs
Open5gs open5gs
Vendors & Products Open5gs
Open5gs open5gs
Type Values Removed Values Added
Description Open 5GS WebUI uses a hard-coded JWT signing key (change-me) whenever the environment variable JWT_SECRET_KEY is unset
Title Open 5GS WebUI uses a hard-coded JWT signing key
References
Weaknesses
  • CWE-798

    Use of Hard-coded Credentials

Sources

Status
PUBLISHED
Assigner
certcc
Published
Updated
Jan 21, 2026, 4:47 PM
Reserved
Jan 5, 2026, 8:12 PM
Status
Analyzed
Published
Jan 20, 2026, 8:16 PM
Modified
Jun 17, 2026, 10:11 AM