1341 matches found
CVE-2024-37051
CVE-2024-37051 Analysis Overview CVE-2024-37051 is a vulnerability found in JetBrains' IntelliJ-based IDEs, affecting the GitHub plugin. It allows unauthorized exposure of GitHub access tokens when a malicious pull request PR is loaded. Technical Details The vulnerability occurs during the...
nuvola
nuvola nuvola with the lowercase n is a tool to dump and perform automatic and manual security analysis on AWS environments configurations and services using predefined, extensible and custom rules created using a simple Yaml syntax. The general idea behind this project is to create an abstracted...
ninjasworkout
Damn Vulnerable NodeJS Application Quick Start Download the Repo = run npm i Afer Installing all dependency just run the application node app.js or nodemon app.js ADDED BUGS Prototype Pollution ✅1 No SQL Injection ✅2 Cross site Scripting ✅3 Broken Access Control ✅4 Broken Session Management ✅5 We...
layne
Layne Layne is a self-hosted GitHub App that centralizes security scanning across our repositories. Since we don't use commercial SAST/secrets scanning tools, nor we have access to GitHub Enterprise, it can get hard to maintain different GitHub Actions workflow files across different repositories...
CVE-2026-129863 GitBucket through 4.48.0 Incorrect Authorization via Pull Request API Endpoints
GitBucket through 4.48.0 contains an incorrect authorization vulnerability that allows authenticated users to edit and merge other users' pull requests because the PATCH pulls and PUT pulls merge REST API endpoints only check read access. Attackers can close, reopen, retitle, retarget, or merge...
CVE-2026-129863
GitBucket versions up to and including 4.48.0 are vulnerable to an incorrect authorization issue within the Pull Request API endpoints. The vulnerability exists because the PATCH pulls and PUT pulls merge REST API endpoints fail to verify write permissions, only checking for read access. Conseque...
CVE-2026-129863 GitBucket through 4.48.0 Incorrect Authorization via Pull Request API Endpoints
GitBucket through 4.48.0 contains an incorrect authorization vulnerability that allows authenticated users to edit and merge other users' pull requests because the PATCH pulls and PUT pulls merge REST API endpoints only check read access. Attackers can close, reopen, retitle, retarget, or merge...
CVE-2026-128365
Removing a team's review request looked up a review by the negated team ID, which for the team with ID 2 is the ID of the built-in Actions user, and marked the review it found as official. In the organization that owns that team, a user who can change the review requests of a pull request could...
CVE-2026-127958
A pull request review created through the API as a draft event set to PENDING or left empty was added to the pull request timeline and announced through notifications and activity feeds like a submitted review. Its body and line comments were therefore visible to everyone who can read the pull...
CVE-2026-129525 Gitea pull request disclosure to members with access to issues only
Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A user who can read a repository's issues but not its pull requests could read pull request data through the issue sub-resources of the API timeline, attachments, labels,...
CVE-2026-129525 Gitea pull request disclosure to members with access to issues only
Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. A user who can read a repository's issues but not its pull requests could read pull request data through the issue sub-resources of the API timeline, attachments, labels,...
CVE-2026-129525
The software Gitea contains a vulnerability where several endpoints handling both issues and pull requests fail to verify the specific type of the addressed item. This allows a user with read access to a repository's issues (but not its pull requests) to access pull request data through issue sub...
CVE-2026-127958 Gitea disclosure of pending pull request reviews created through the API
A pull request review created through the API as a draft event set to PENDING or left empty was added to the pull request timeline and announced through notifications and activity feeds like a submitted review. Its body and line comments were therefore visible to everyone who can read the pull...
CVE-2026-127958
The Gitea version associated with CVE-2026-127958 contains a vulnerability where pull request reviews created via the API as a draft (with event set to PENDING or left empty) were incorrectly added to the pull request timeline. This caused review bodies and line comments to be visible to anyone w...
CVE-2026-127958 Gitea disclosure of pending pull request reviews created through the API
A pull request review created through the API as a draft event set to PENDING or left empty was added to the pull request timeline and announced through notifications and activity feeds like a submitted review. Its body and line comments were therefore visible to everyone who can read the pull...
CVE-2026-123642
In Gitea , a vulnerability exists where the AGit flow (pushing to refs/for/...) fails to re-verify a pusher's permissions when creating a pull request. This allows a user or deploy key with only read access to the code, or write access to the wiki over SSH, to open pull requests in a repository w...
CVE-2026-123642 Gitea pull request creation without pull request access through AGit
The AGit flow pushing to refs/for/... did not check the pusher's access to pull requests again when it created the pull request. A user or deploy key with read access to the code only, or with write access to the wiki over SSH, could open pull requests in a repository where they have no access to...
CVE-2026-123642 Gitea pull request creation without pull request access through AGit
The AGit flow pushing to refs/for/... did not check the pusher's access to pull requests again when it created the pull request. A user or deploy key with read access to the code only, or with write access to the wiki over SSH, could open pull requests in a repository where they have no access to...
Attacker Used 4,837 Hijacked GitHub Accounts to Run a CI Secret Stealer in 1,806+ Repositories
Starting Tuesday, an attacker used stolen credentials for 4,837 GitHub accounts to plant a secret stealer in repositories those accounts could write to, according to Aikido Security, a security software company. The stealer is built to take the secrets and cloud credentials that a repository's CI...
DHI-RBB6-EUUR-4WLK-PZEW For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped…
For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters exclude execution. A fork pull request author can supply a workflow matching a required status context but deliberately prevent it from...