Security readout for executives and security teams
Plain-English summary
A user with ordinary access can reportedly promote their own account to administrator on affected JUNG smart home servers. Administrative control could allow changes to devices, network settings, and other system functions, creating serious confidentiality, integrity, and availability risks.
Executive priority
Treat affected, reachable systems as a prompt remediation priority, especially where they control security-sensitive or operational devices. Contain management access immediately and seek vendor guidance. Urgency is high, although the supplied evidence does not establish active exploitation.
Technical view
JUNG eNet SMART HOME server versions 2.2.1 (46056) and 2.3.1 (46841) reportedly lack sufficient authorization in the setUserGroup JSON-RPC method. An authenticated UG_USER can target their own username through the network-accessible management endpoint and obtain UG_ADMIN privileges. The issue is classified as CWE-269 with CVSS 3.1 score 8.8.
Likely exposure
Exposure requires an affected server version, a valid low-privileged account, and network access to the management interface. Risk is greater where that interface is reachable from untrusted networks or user accounts are broadly distributed. The supplied sources identify no additional affected versions.
Exploitation context
The reported attack has low complexity, requires low privileges, and needs no user interaction. Successful exploitation could grant administrative capabilities. The CVE is not identified as KEV, and the supplied sources provide no evidence of active exploitation in the wild.
Researcher notes
The authorization failure is specifically reported in setUserGroup under /jsonrpc/management. Impact claims align with the supplied CVSS vector, which indicates complete confidentiality, integrity, and availability impact without scope change. Public evidence supplied here does not identify a patched version, vendor workaround, exploitation telemetry, or broader version range.
Mitigation direction
- Inventory JUNG eNet SMART HOME servers and identify the exact installed version and build.
- Restrict management-interface access to trusted administrators and networks while remediation is evaluated.
- Disable unnecessary user accounts and review whether each remaining account requires access.
- Check current JUNG guidance for an update or vendor-approved mitigation; no fix is named in the supplied sources.
- Monitor account-group changes and investigate unexpected promotions to UG_ADMIN.
Validation and detection
- Confirm whether each server runs version 2.2.1 (46056) or 2.3.1 (46841).
- Verify the management interface is not reachable from untrusted networks.
- Review current account memberships for unexpected or unauthorized UG_ADMIN assignments.
- Examine available audit and request logs for suspicious setUserGroup activity.
- After vendor remediation, verify low-privileged users cannot alter account groups without authorization.
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-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-26369 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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:L/UI:N/S:U/C:H/I:H/A:H2.85.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ZeroScience Vulnerability Advisory ZSL-2026-5975CVE reference, VulnCheck · third-party-advisory
- VulnCheck Advisory: JUNG eNet SMART HOME server 2.2.1/2.3.1 Privilege Escalation via setUserGroupCVE reference, VulnCheck · third-party-advisory
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.
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.