LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21874: NiceGUI has Redis connection leak via tab storage causes service degradation

NiceGUI is a Python-based UI framework. From versions v2.10.0 to 3.4.1, an unauthenticated attacker can exhaust Redis connections by repeatedly opening and closing browser tabs on any NiceGUI application using Redis-backed storage. Connections are never released, leading to service degradation when Redis hits its connection limit. NiceGUI continues accepting new connections - errors are logged but the app stays up with broken storage functionality. This issue has been patched in version 3.5.0.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-21874 affects NiceGUI applications that use Redis-backed storage. An unauthenticated person can repeatedly open and close browser tabs, causing Redis connections to leak until Redis reaches its connection limit. The application may remain running, but storage-dependent features can degrade or break. The issue is patched in NiceGUI 3.5.0.

Executive priority

Treat as a moderate availability risk. It is unlikely to expose data based on current sources, but it can disrupt application functionality for affected deployments. Upgrade exposed NiceGUI applications using Redis-backed storage during the next planned remediation window, sooner for customer-facing services.

Technical view

NiceGUI versions 2.10.0 through 3.4.1 do not release Redis connections tied to tab storage. The weakness is CWE-772: missing release of resources after effective lifetime. The CVSS 3.1 score is 5.3, network exploitable, low complexity, no privileges or user interaction, with low availability impact and no confidentiality or integrity impact reported.

Likely exposure

Exposure is likely for internet- or network-accessible NiceGUI applications running versions >=2.10.0 and <3.5.0 with Redis-backed storage enabled. NiceGUI deployments not using Redis-backed storage are not identified as affected in the provided sources.

Exploitation context

The source bundle does not indicate known active exploitation, and KEV is false. Exploitation does not require authentication and can be performed through normal browser behavior repeated at scale, causing Redis connection exhaustion and degraded storage functionality.

Researcher notes

The public sources describe the vulnerable condition and patch but do not provide evidence of exploitation in the wild. Analysis should focus on Redis-backed storage lifecycle behavior before and after commit 6c52eb2c90c4b67387c025b29646b4bc1578eb83, without assuming impact beyond service degradation and broken storage functionality.

Mitigation direction

  • Upgrade NiceGUI to version 3.5.0 or later.
  • Prioritize applications using Redis-backed storage and exposed to untrusted users.
  • Review the GitHub advisory and release notes for vendor-specific guidance.
  • Monitor Redis connection usage until all affected deployments are upgraded.

Validation and detection

  • Inventory NiceGUI application versions across production and staging.
  • Identify which NiceGUI applications use Redis-backed storage.
  • Confirm affected deployments are below version 3.5.0.
  • Check Redis logs and metrics for connection-limit errors.
  • After upgrading, verify Redis connections are released during tab close activity.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-772: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2026-21874 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-21874Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
zauberzeugnicegui>= 2.10.0, < 3.5.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-772 · source CWE mapping

Missing Release of Resource after Effective Lifetime

Missing Release of Resource after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.