CVE-2026-130713
NocoDB before 2026.10.1 contains a user enumeration vulnerability that allows unauthenticated attackers to identify pending invitees through
CVSS
3.7
Bajo
EPSS
—
KEV
—
Exploit Today
0
0-100
Publicado: 18 nov 2026 · Última mod.: 19 nov 2026 · CWE-204
Sin historial EPSS suficiente todavía.
NocoDB before 2026.10.1 contains a user enumeration vulnerability that allows unauthenticated attackers to identify pending invitees through a distinct sign-in error message. Attackers can submit sign-in requests where validateUser in auth.service.ts skips password comparison for saltless invited accounts, confirming the email address has an account.
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-765456.5 MED—
———In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could determine whether a username exists through the Representational State Transfer (REST) API or Splunk Web and lock out existing user accounts through repeated login attempts.
The vulnerability is possible because Splunk Enterprise returns different login failure responses for locked existing user accounts and nonexistent usernames.6hCVE-2026-1330996.5 MED—
———In JetBrains TeamCity before 2026.2.2 vCS root passwords could be extracted via the REST API property locator4hCVE-2026-1307143.7 BAJ—
——0NocoDB before 2026.10.1 contains a user enumeration vulnerability that allows unauthenticated attackers to determine registered email addresses by observing differing sign-up endpoint responses. Attackers can submit addresses to signup in users.service.ts and compare error messages to identify existing accounts and pending Enterprise invitations, even under invite-only signup.4hCVE-2026-129279—46.4%
——14The password reset function in N-able N-central before 2026.4.1 HF3 returns distinguishable responses for valid and invalid accounts. A remote, unauthenticated attacker can enumerate the email addresses of valid user accounts.2dCVE-2026-1303625.3 MED17.3%
——5phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an account enumeration vulnerability that allows unauthenticated attackers to identify valid logins through differing POST /api/webauthn/prepare responses. Attackers can submit wordlists of usernames, reusing one unconsumed CSRF token without rate limiting, to discover administrator logins for password spraying and phishing.1dCVE-2026-105671—43.7%
——13The login flow in Zenitel Connect before 1.11.0 returns different error responses depending on whether a submitted username exists, which allows remote attackers to enumerate valid user accounts via crafted login requests.6d