Export limit exceeded: 377403 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (142 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-28744 | 1 Gitea | 1 Gitea Open Source Git Server | 2026-07-06 | 8.1 High |
| Gitea versions up to and including 1.26.1 allow Git smart HTTP requests authenticated with bearer tokens to bypass repository token scope checks. | ||||
| CVE-2026-58418 | 1 Gitea | 1 Gitea Open Source Git Server | 2026-07-06 | 6.5 Medium |
| SSRF via HTTP Redirect in Repository Migration | ||||
| CVE-2026-58419 | 1 Gitea | 1 Gitea Open Source Git Server | 2026-07-06 | 7.5 High |
| Notification API leaks private issue metadata after access revocation | ||||
| CVE-2026-58421 | 1 Gitea | 1 Gitea Open Source Git Server | 2026-07-06 | 7.5 High |
| Unauthenticated ReDoS via CODEOWNERS pattern matching allows denial of service | ||||
| CVE-2026-58422 | 1 Gitea | 1 Gitea Open Source Git Server | 2026-07-06 | 9.8 Critical |
| Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts | ||||
| CVE-2026-58423 | 1 Gitea | 1 Gitea Open Source Git Server | 2026-07-06 | 7.7 High |
| LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositories | ||||
| CVE-2026-58424 | 1 Gitea | 1 Gitea Open Source Git Server | 2026-07-06 | 8.9 High |
| Permanent Fork PR Workflow Approval Gate Bypass | ||||
| CVE-2026-58426 | 1 Gitea | 1 Gitea Open Source Git Server | 2026-07-06 | 9.6 Critical |
| Gitea Actions Artifacts V4 signed URL HMAC ambiguity allows cross-repository artifact read and cross-task upload-state write | ||||
| CVE-2026-58053 | 1 Gitea | 1 Act Runner | 2026-06-30 | 9.9 Critical |
| Gitea act_runner with the Docker backend (through act 0.262.0) passes a workflow's container.options string to the Docker job container's HostConfig and, when configured with privileged: false, forces only the Privileged flag off while merging options such as --pid=host, --cap-add, and --security-opt unchanged. A user who can run a workflow on a Docker-backed runner can create a job container with host namespaces and broad capabilities and escape to the host as root despite privileged mode being disabled. | ||||
| CVE-2026-20750 | 1 Gitea | 1 Gitea | 2026-04-18 | 9.1 Critical |
| Gitea does not properly validate project ownership in organization project operations. A user with project write access in one organization may be able to modify projects belonging to a different organization. | ||||
| CVE-2026-20897 | 1 Gitea | 1 Gitea | 2026-04-18 | 9.1 Critical |
| Gitea does not properly validate repository ownership when deleting Git LFS locks. A user with write access to one repository may be able to delete LFS locks belonging to other repositories. | ||||
| CVE-2026-20904 | 1 Gitea | 1 Gitea | 2026-04-18 | 6.5 Medium |
| Gitea does not properly validate ownership when toggling OpenID URI visibility. An authenticated user may be able to change the visibility settings of other users' OpenID identities. | ||||
| CVE-2026-0798 | 1 Gitea | 1 Gitea | 2026-04-18 | 3.5 Low |
| Gitea may send release notification emails for private repositories to users whose access has been revoked. When a repository is changed from public to private, users who previously watched the repository may continue to receive release notifications, potentially disclosing release titles, tags, and content. | ||||
| CVE-2026-20736 | 1 Gitea | 1 Gitea | 2026-04-18 | 7.5 High |
| Gitea does not properly verify repository context when deleting attachments. A user who previously uploaded an attachment to a repository may be able to delete it after losing access to that repository by making the request through a different repository they can access. | ||||
| CVE-2026-20800 | 1 Gitea | 1 Gitea | 2026-04-18 | 6.5 Medium |
| Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications. | ||||
| CVE-2026-20883 | 1 Gitea | 1 Gitea | 2026-04-18 | 6.5 Medium |
| Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches. | ||||
| CVE-2026-20888 | 1 Gitea | 1 Gitea | 2026-04-18 | 4.3 Medium |
| Gitea does not properly verify authorization when canceling scheduled auto-merges via the web interface. A user with read access to pull requests may be able to cancel auto-merges scheduled by other users. | ||||
| CVE-2026-20912 | 1 Gitea | 1 Gitea | 2026-04-18 | 9.1 Critical |
| Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users. | ||||
| CVE-2024-6886 | 1 Gitea | 1 Gitea | 2026-04-15 | 8.8 High |
| Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Gitea Gitea Open Source Git Server allows Stored XSS.This issue affects Gitea Open Source Git Server: 1.22.0. | ||||
| CVE-2025-69413 | 1 Gitea | 1 Gitea | 2026-01-06 | 5.3 Medium |
| In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists. | ||||