CVE-2026-132940
In JetBrains TeamCity before 2026.2 credential leakage via Mercurial subrepository URLs was possible
CVSS
6.4
Média
EPSS
—
KEV
—
Exploit Today
0
0-100
Publicado: 19 de nov. de 2026 · Última mod.: 19 de nov. de 2026 · CWE-201
Ainda não há histórico EPSS suficiente.
In JetBrains TeamCity before 2026.2 credential leakage via Mercurial subrepository URLs was possible
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-1312667.7 ALT—
———In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could cause Splunk SOAR to send a stored Elasticsearch password to a host that the user controls.
The vulnerability is possible because Splunk SOAR reuses a stored Elasticsearch password for a changed Search Settings endpoint without requiring a replacement password.6hCVE-2026-1331082.7 BAI—
———In JetBrains TeamCity before 2026.2.2 the current request details debug endpoint exposed authentication headers and session cookies4hCVE-2026-1330847.7 ALT—
———In JetBrains TeamCity before 2026.2.2, 2026.1.6 vCS root credentials could be exposed via change viewer links4hCVE-2026-1329027.7 ALT—
——0In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 access keys of parent project AWS connections could be disclosed4hCVE-2026-1329007.5 ALT—
——0In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 secure parameter values were disclosed to project viewers in pipelines4hCVE-2026-1299926.3 MÉD—
——0Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.0, failed Railpack builds and database backups propagate an execution error containing the full command, exposing application environment variables, database passwords, and S3 access keys embedded in those commands. When the corresponding App Build Error or Database Backup notification setting is enabled, the disclosure can send secrets to email, Slack, Discord, Telegram, or webhooks; the same secrets are written separately to persistent Dokploy container logs, which may be accessible to more principals than the affected service. This issue is fixed in version 0.31.0.10h