Security readout for executives and security teams
Plain-English summary
Open5GS WebUI can fall back to a known JWT signing secret, "change-me," when JWT_SECRET_KEY is not configured. If the WebUI is reachable, this can undermine trust in login/session tokens and may allow unauthorized access or changes. The issue is rated medium, but urgency rises for exposed telecom lab or core-management environments.
Executive priority
Treat as a configuration-dependent medium-risk issue. Prioritize exposed Open5GS WebUI systems and any environment supporting telecom testing, private 5G, or core-network management. The immediate business action is to confirm a unique JWT secret and reduce WebUI exposure.
Technical view
CVE-2026-0622 is a CWE-798 hard-coded credential issue in Open5GS WebUI. The CVE states the WebUI uses a hard-coded JWT signing key when JWT_SECRET_KEY is unset. CVSS 3.1 is 6.5: network exploitable, low complexity, no privileges or user interaction, with low confidentiality and integrity impact and no availability impact.
Likely exposure
Systems running Open5GS WebUI are most exposed when JWT_SECRET_KEY is unset, left at the fallback value, or WebUI is network-accessible. The CVE record does not provide precise affected version ranges beyond the listed Open5GS product data, so organizations should validate configuration directly.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk comes from a publicly described default signing secret condition. Attackers would need network reachability to the WebUI and a deployment where the secret was not explicitly configured.
Researcher notes
Evidence is limited to the CVE description and linked public references. The affected version data is not granular, and the bundle does not name a definitive patch level. The most important validation point is whether JWT_SECRET_KEY is unset or default-dependent in running deployments.
Mitigation direction
- Set JWT_SECRET_KEY to a strong, unique secret in every WebUI deployment.
- Do not expose Open5GS WebUI directly to untrusted networks.
- Review Open5GS and CERT guidance for version-specific fixes or updates.
- Rotate the JWT secret if exposure or default use is suspected.
- Restrict administrative access with network controls and authentication layers.
Validation and detection
- Inventory all Open5GS WebUI instances and their network exposure.
- Check whether JWT_SECRET_KEY is explicitly configured.
- Confirm the configured secret is not the documented fallback value.
- Review WebUI access logs for suspicious administrative activity.
- Track linked GitHub and CERT references for remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-0622 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/open5gs/open5gs/issues/2264CVE reference
- https://github.com/open5gs/open5gs/issues/856CVE reference
- https://github.com/open5gs/open5gs/pull/857CVE reference
- https://www.kb.cert.org/vuls/id/458022CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.