PULSE
FEED
ransomakira reclama a Ligne Roset · FR · Retail & E-Commerceransomakira reclama a Houston Machine and Thread · US · Manufacturingransomdirewolf reclama a Algonomy · US · Technologyransomobsoft reclama a Company #6ransomakira reclama a Hudson & Hudson SignProducts · US · Manufacturingransomshiba reclama a Istituto Borgo · IT · Otherransomakira reclama a Boyle, Pecharich, Cline, Whittington andStallings · Professional Servicesransomn0n reclama a Dompé Farmaceutici S.p.A. · IT · Healthcareransomn0n reclama a Cogent Biosciences, Inc. · US · Healthcareransomn0n reclama a Chartboost LLC · US · Technologyransomn0n reclama a Centrepoint · SA · Energy & Utilitiesransomn0n reclama a Resource Consultants · US · Professional Servicesransomqilin reclama a Rotstein & Shiffman · IL · Professional Servicesransomn0n reclama a Max Fashion · AE · Retail & E-Commerceransomakira reclama a Ligne Roset · FR · Retail & E-Commerceransomakira reclama a Houston Machine and Thread · US · Manufacturingransomdirewolf reclama a Algonomy · US · Technologyransomobsoft reclama a Company #6ransomakira reclama a Hudson & Hudson SignProducts · US · Manufacturingransomshiba reclama a Istituto Borgo · IT · Otherransomakira reclama a Boyle, Pecharich, Cline, Whittington andStallings · Professional Servicesransomn0n reclama a Dompé Farmaceutici S.p.A. · IT · Healthcareransomn0n reclama a Cogent Biosciences, Inc. · US · Healthcareransomn0n reclama a Chartboost LLC · US · Technologyransomn0n reclama a Centrepoint · SA · Energy & Utilitiesransomn0n reclama a Resource Consultants · US · Professional Servicesransomqilin reclama a Rotstein & Shiffman · IL · Professional Servicesransomn0n reclama a Max Fashion · AE · Retail & E-Commerce
← Todos os CVEs
CVE Watch14 de out. de 2026

CVE-2026-108522

A vulnerability was found in Studio-Saelix Sencho up to 0.94.1. This affects an unknown part of the file /api/auth/login of the component Lo

CVSS

8.3

Alta

EPSS

0.4%

p36

KEV

—

Exploit Today

11

0-100

Publicado: 11 de out. de 2026 · Última mod.: 14 de out. de 2026 · CWE-287

EPSS · 30d
0.4%EPSS · 30 dias0.4%
2026-10-112026-11-05
Descrição técnica

A vulnerability was found in Studio-Saelix Sencho up to 0.94.1. This affects an unknown part of the file /api/auth/login of the component Login Endpoint. Performing a manipulation of the argument X-Forwarded-For results in improper authentication. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The patch is named 79b86ddcd4aefdd6941f098e35990ab397b13c72. To fix this issue, it is recommended to deploy a patch. The vendor confirms: "The login limiter relied on client-supplied X-Forwarded-For data without an explicit trusted-proxy boundary, allowing an attacker to rotate the apparent client address. The remediation now ignores forwarding headers by default, accepts them only from explicitly configured proxy CIDRs, and adds a separate failed-attempt limit keyed by normalized account identity."

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-973676.4 MÉD
—
———A flaw was found in the Keycloak Account REST API where it incorrectly handles session identification. A malicious client owner can manipulate their own security tokens to point to a different user's active session. This allows the attacker to access and modify the victim's account information, potentially leading to a full account takeover by changing the recovery email and resetting the password.9h
CVE-2026-964474.2 MÉD
—
———A flaw was found in the TokenManager component of Keycloak, an open-source identity and access management solution. The issue occurs during the validation of stateless access tokens when the original user ID no longer exists. Keycloak incorrectly falls back to using the username to identify the user without verifying if the identity matches the original token subject. This could allow an attacker with an old token to gain access to a newly created service account if it shares the same client ID as a previously deleted one.9h
CVE-2026-196886.8 MÉD
—
———A flaw was found in the Admin REST API of Keycloak, an identity and access management solution. The Admin API fails to verify the intended audience of bearer tokens during authentication. This issue allows an attacker who operates a client within a realm to capture an administrator's access token and reuse it to perform unauthorized administrative actions, potentially leading to full realm compromise.9h
CVE-2026-1109559.8 CRÍ
—
———The Wurdey WordPress plugin through 1.0.0 does not verify a request signature before logging a user in, allowing unauthenticated attackers to authenticate as an administrator knowing only the administrator's username.7h
CVE-2026-492728.5 ALT
—
———OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. From 3.3.0 until 4.0.1, OAuthLib's RFC 8628 device workflow does not require DeviceCodeGrant.validate_token_request to check that the device_code parameter is present and valid. A caller whose client request is accepted by the configured validator and who knows a valid client ID enabled for the device workflow can submit a missing or bogus device code to the token endpoint and obtain a bearer token without completing device authorization. This issue is fixed in version 4.0.1.22h
CVE-2026-978477.1 ALT
—
——0A flaw was found in the protocol mapper and identity resolution components of Keycloak. The issue occurs when a client manager uses hardcoded-claim mappers to override identity claims in sessionless service-account tokens. Because these tokens lack a session ID, Keycloak may incorrectly resolve the token bearer as a different, highly privileged user based on the manipulated claims. This can allow an attacker with limited client management permissions to impersonate a realm administrator and gain full control over the realm.9h