47 matches found
CVE-2026-133041
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible...
CVE-2026-133041
In JetBrains TeamCity versions before 2026.2.1 and 2026.1.5 , a Stored Cross-Site Scripting (XSS) vulnerability exists within the Commit Status Publisher settings . This flaw is caused by improper neutralization of input during web page generation (CWE-79 ). The vulnerability allows an attacker w...
EUVD-2026-129813
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible...
CVE-2026-133041
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible...
CVE-2026-133041: JetBrains TeamCity: In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible...
CVE-2026-123006 Gitea password hash disclosure through repository search
The repository search used by the dashboard GET /repo/search returned the internal commit status object of each repository. Since 28.0.0 that object included the repository owner's full user record, so any signed-in user could read the password hash, salt and email address of the owner of any...
CVE-2026-123006 Gitea password hash disclosure through repository search
The repository search used by the dashboard GET /repo/search returned the internal commit status object of each repository. Since 28.0.0 that object included the repository owner's full user record, so any signed-in user could read the password hash, salt and email address of the owner of any...
CVE-2026-123006 Gitea password hash disclosure through repository search
The repository search used by the dashboard GET /repo/search returned the internal commit status object of each repository. Since 28.0.0 that object included the repository owner's full user record, so any signed-in user could read the password hash, salt and email address of the owner of any...
CVE-2026-123006
The Gitea repository search functionality, specifically the GET /repo/search endpoint used by the dashboard, is vulnerable to a password hash disclosure vulnerability. In versions since 28.0.0 , the internal commit status object returned by this endpoint included the repository owner's full user ...
PT-2026-148050
The repository search used by the dashboard GET /repo/search returned the internal commit status object of each repository. Since 28.0.0 that object included the repository owner's full user record, so any signed-in user could read the password hash, salt and email address of the owner of any...
EUVD-2019-16352
Malware in sbrugna...
EUVD-2023-38317
Malicious code in bioql PyPI...
CVE-2023-34220
In JetBrains TeamCity before 2023.05 stored XSS in the Commit Status Publisher window was possible...
CVE-2019-6794
An issue was discovered in GitLab Community and Enterprise Edition before 11.5.8, 11.6.x before 11.6.6, and 11.7.x before 11.7.1. It allows Information Disclosure issue 5 of 6. A project guest user can view the last commit status of the default branch...
CVE-2024-36371
In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible...
CVE-2024-36371
In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible...
CVE-2024-36364
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 improper access control in Pull Requests and Commit status publisher build features was possible...
CVE-2024-36364
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 improper access control in Pull Requests and Commit status publisher build features was possible...
CVE-2024-36371
In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible...
CVE-2024-36371
JetBrains TeamCity versions prior to 2023.05.6 and 2023.11.5 are affected by a stored cross-site scripting (XSS) vulnerability in the Commit status publisher, caused by insufficient filtering/escaping of user-provided data. An attacker could inject arbitrary script or HTML via the publisher, pote...