PULSE
FEED
ransompixelleaks reclama a KDBS Solutions (client hosting) · Technologyransompixelleaks reclama a Proymoda (proymoda.com.mx) · MX · Retail & E-Commerceransomhelix reclama a Veritiv · US · Manufacturingransomvortex reclama a Drive Medical - 1,442,814 records · US · Healthcareransomhelix reclama a Sonoco · US · Manufacturingransomendzone reclama a West-Com Nurse Call Systems, Inc · US · Healthcareransomcurious worm reclama a examinetics.com · US · Healthcareransombraincipher reclama a intelligentaudit.com · US · Professional Servicesransombraincipher reclama a roedentallab.com · DE · Healthcareransombraincipher reclama a edi-uae.com · AE · Professional Servicesransombraincipher reclama a havingbabies.com · AU · Healthcareransomaoqin reclama a Esco Optics · US · Manufacturingransompayload reclama a WWGlas · DE · Manufacturingransomthegentlemen reclama a Rosenberger Legal · DE · Professional Servicesransompixelleaks reclama a KDBS Solutions (client hosting) · Technologyransompixelleaks reclama a Proymoda (proymoda.com.mx) · MX · Retail & E-Commerceransomhelix reclama a Veritiv · US · Manufacturingransomvortex reclama a Drive Medical - 1,442,814 records · US · Healthcareransomhelix reclama a Sonoco · US · Manufacturingransomendzone reclama a West-Com Nurse Call Systems, Inc · US · Healthcareransomcurious worm reclama a examinetics.com · US · Healthcareransombraincipher reclama a intelligentaudit.com · US · Professional Servicesransombraincipher reclama a roedentallab.com · DE · Healthcareransombraincipher reclama a edi-uae.com · AE · Professional Servicesransombraincipher reclama a havingbabies.com · AU · Healthcareransomaoqin reclama a Esco Optics · US · Manufacturingransompayload reclama a WWGlas · DE · Manufacturingransomthegentlemen reclama a Rosenberger Legal · DE · Professional Services
← Todos los CVEs
CVE Watch17 nov 2026

CVE-2026-71304

Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, check_client_auth() in sr

CVSS

8.8

Alto

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 17 nov 2026 · Última mod.: 17 nov 2026 · CWE-613

EPSS · 30d

Sin historial EPSS suficiente todavía.

Descripción técnica

Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, check_client_auth() in src/api/auth.c detects that a matching session identifier has passed valid_until but still assigns user_id before the expired state can be rejected. That assignment sends execution through the authorized branch, renews valid_until for another timeout interval, and leaves the session-expired response unreachable. An attacker who possesses a previously valid session identifier can periodically reuse it to preserve administrative access indefinitely, making the configured session timeout ineffective. This issue is fixed in version 6.7.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-820385.9 MED
—
———Bludit through 3.22.0 contains an improper session invalidation vulnerability that allows demoted users to retain revoked privileges because Login::isLogged() never re-reads the session-stored role. Attackers holding a session issued while their account was an administrator can keep using it after demotion to perform administrator actions such as creating new administrator accounts.10h
CVE-2026-1233526.5 MED
—
———HomeBox is a home inventory and organization system. Prior to 0.27.0, a HomeBox password change revokes the user's other session tokens but does not revoke the user's API keys, and API keys have no default API-key expiration. An attacker who has obtained an API key can therefore retain full API-level access after the account owner changes the password and can keep that access indefinitely unless the owner discovers and manually deletes the key by ID. Because the password change terminates other sessions, the surviving API credential can evade the owner's expected containment and detection. This issue is fixed in version 0.27.0.10h
CVE-2026-21165—
—
——0Insufficient session expiration in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to bypass device authentication. User interaction is required for triggering this vulnerability.12h
CVE-2026-129706—
19.4%
——6In the vulnerability-lookup web application, the Flask-Login session identifier was set to the bare numeric user ID (User.get_id() returned self.id). Because the session ID contained no component derived from the user's credential, it remained valid indefinitely regardless of any subsequent password change, account recovery, or administrator-initiated password reset. An attacker who had obtained a valid session for a user account (for example through cross-site scripting, session hijacking, or a previously exposed feed or API key) could continue to access that user's account after the user changed their password, because the session cookie still carried the same static user ID and the user_loader accepted it without any credential-bound validation. The affected component is the session management layer of the vulnerability-lookup Flask application, specifically the User.get_id() method in website/models/user.py and the load_user callback in website/web/views/session_mgmt.py. The vulnerability required that an attacker already possessed a valid session for the target user; no additional authentication or special deployment configuration was needed beyond a standard deployment of the application. The security impact is that a user cannot effectively revoke an attacker's access by changing their password, performing an account recovery, or having an administrator reset the credential. The attacker retains full authenticated access to the user's profile, subscriptions, and any role-gated functionality for the lifetime of the session cookie. Additionally, sessions that were opened via a feed key or API key before a prior fix (commit 3605d5b6) also persisted indefinitely.2d
CVE-2026-129703—
24.5%
——7In the vulnerability-lookup web application, the authentication decorators for feed-key requests (auth_feedkey_func in website/decorators.py) and API-key requests (auth_func in website/web/api/v1/common.py) called Flask-Login's login_user() function. This caused the HTTP response to a request authenticated solely by a feed key (supplied as the X-FEED-KEY URL parameter) or an API key (supplied as the X-API-KEY header) to set a session cookie that grants full authenticated access to every page in the application, without requiring a password or two-factor authentication. The practical impact is that any party possessing a leaked feed URL (a common occurrence, as feed URLs are shared with RSS readers) or an API key could obtain a valid web session for the associated account. This session provides access to the user's account page, which exposes the API key and other profile data, and for accounts with the administrator role, access to the /admin interface, enabling full administrative control of the application. The vulnerability affects all users whose feed key or API key is exposed. No prior authentication, user interaction, or special network conditions are required; a single HTTP request with the token is sufficient to establish the session. The session persists until it expires, and because it is not bound to the original credential (a related CWE-613 issue noted by the developers), revoking the feed key or API key does not invalidate the already-created session. The fix replaces the login_user() call with assignment to g._login_user, which Flask-Login's current_user property reads for the current request only, without writing any session cookie. The affected views remain unchanged and continue to see the authenticated user for the single request.2d
CVE-2026-1283595.4 MED
4.1%
——1When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged for new tokens, so applications that sign users in through Gitea kept them signed in. The token endpoint now refuses users who may not sign in, and token introspection reports their tokens as inactive.1d