Export limit exceeded: 428129 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428129 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (428129 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-123642 | 1 Gitea | 1 Gitea | 2026-11-17 | 4.3 Medium |
| 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 pull requests. Creating a pull request through AGit now requires read access to the pull requests of the repository and is refused for wiki pushes. | ||||
| CVE-2026-127958 | 1 Gitea | 1 Gitea | 2026-11-17 | 5.3 Medium |
| 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 request, including anonymous visitors of a public repository, before the reviewer submitted it. Pending reviews no longer get a timeline entry or notifications until they are submitted. | ||||
| CVE-2026-128365 | 1 Gitea | 1 Gitea | 2026-11-17 | 3.1 Low |
| 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 make an approval left by the Actions user count toward the approvals required by branch protection. Merging still required permission to merge. Removing a team review request no longer changes any review. | ||||
| CVE-2026-129341 | 1 Gitea | 1 Gitea | 2026-11-17 | 5.4 Medium |
| The web endpoint that removes an attachment skipped the permission check when the request came from the user who had uploaded the attachment, and it was reachable with read access to issues or pull requests. A user who had uploaded a release asset could still delete it after losing write access to the repository. The endpoint now only deletes attachments that the user uploaded and that are not yet linked to an issue, comment or release. | ||||
| CVE-2026-130506 | 2026-11-17 | 8.8 High | ||
| An out-of-bounds write flaw was found in virglrenderer, the host-side 3D renderer used by virtual machines with virtio-gpu OpenGL acceleration enabled. A malicious guest VM can send a crafted pair of linked shaders that triggers an out-of-bounds memory write on the host during shader translation, before any GL call is made. This can crash the host renderer process and may allow further impact. | ||||
| CVE-2026-95782 | 1 Hpe | 1 Private 5g Core | 2026-11-16 | 7.5 High |
| A vulnerability exists in a monitoring component that may, under certain conditions, allow security controls to be circumvented. Successful exploitation could result in unauthorized access to information intended for authorized users only. | ||||
| CVE-2026-95784 | 1 Hpe | 1 Private 5g Core | 2026-11-16 | 7.5 High |
| A vulnerability exists in a system component that may, under certain conditions, disrupt the availability of affected services. Successful exploitation could result in temporary service interruption or loss of functionality. | ||||
| CVE-2026-120729 | 1 Gitea | 1 Gitea | 2026-11-16 | 5.4 Medium |
| The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of the response as HTML. A user who can post a comment or other rendered content could add a link that is displayed as an ordinary issue reference but points to a file in a repository they control, so that the popup inserted that file's content into the page of anyone hovering the link and ran script in the viewer's session. The popup now requests the issue by the owner, repository and index parsed from the link. | ||||
| CVE-2026-120991 | 1 Gitea | 1 Gitea | 2026-11-16 | 6.5 Medium |
| When a container blob upload was rejected, for example because it exceeded a package size quota, the cleanup removed the blob from storage even if the same content already existed and was used by other packages. On an instance with a package quota configured, a user who can upload container images and has the exact content of another owner's package file or image layer could make it undownloadable. The cleanup now only removes blobs that the failed upload created. | ||||
| CVE-2026-123002 | 1 Gitea | 1 Gitea | 2026-11-16 | 7.5 High |
| Gitea accepted an unlimited number of wrong TOTP passcodes during sign-in, in the password reset flow and for Basic authentication with the `X-Gitea-OTP` header. An attacker who already knows an account's password could guess the six-digit passcode by trying codes at a high rate and sign in despite two-factor authentication. After five failed passcodes, further attempts for the account are now refused for 15 minutes. | ||||
| CVE-2026-130072 | 1 Coderaiser | 1 Cloudcmd | 2026-11-16 | 9.1 Critical |
| Cloud Commander (cloudcmd) before 19.21.4 contains an authentication bypass and path traversal vulnerability that allows unauthenticated attackers to rename files by sending PUT /rename requests handled before authentication middleware. Attackers can supply absolute or ../ paths in the from and to arrays to move any file the Node.js process can access outside the configured root, causing data loss or denial of service. | ||||
| CVE-2026-45016 | 1 Egroupware | 1 Egroupware | 2026-11-16 | N/A |
| EGroupware is a web-based groupware server written in PHP. Prior to 23.1.20260601 and 26.5.20260507, the processURL2InlineImages logic in api/src/Mail.php treats non-HTTP image sources in an HTML mail body as local paths and passes a decoded attacker-controlled file:// URI to file_get_contents. Any authenticated user with mail access can cause files readable by the web server process to be embedded as inline MIME attachments in outgoing email, exposing local configuration, credentials, private keys, or other server files. This issue is fixed in versions 23.1.20260601 and 26.5.20260507. | ||||
| CVE-2026-76823 | 1 Opencti-platform | 1 Opencti | 2026-11-16 | N/A |
| OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260706.0, the logsWorkerConfig GraphQL query is authorized with the broad CONNECTORAPI capability and returns Elasticsearch connection details including elasticsearch_username, elasticsearch_password, elasticsearch_api_key, the URL, index, proxy, and TLS-verification setting. A holder of any connector API bearer token can retrieve this credential material. If the returned credentials are valid and Elasticsearch is reachable, the caller can directly read, modify, or delete OpenCTI indices and audit history outside application-layer role, marking, organization, and audit controls, with the practical impact bounded by the credentials' privileges and network reachability. This issue is fixed in version 7.260706.0. | ||||
| CVE-2026-123009 | 1 Gitea | 1 Gitea | 2026-11-16 | 4.3 Medium |
| When a file is edited in a fork through the web editor, Gitea can first copy a branch from the base repository into the fork. That copy did not check whether the user may read the base repository's code. A user who had forked a repository and later lost access to it, for example after it was made private or they were removed as a collaborator, could keep copying its current branches into their fork and read them. The copy now requires read access to the code of the base repository. | ||||
| CVE-2026-123638 | 1 Gitea | 1 Gitea | 2026-11-16 | 8.3 High |
| The "Protected file patterns" setting of a branch protection rule was checked against file names as git prints them, and git quotes names that contain a double quote, a backslash or a control character. Such names never matched a pattern, so a user with write access could add or change files under a protected pattern by direct push or through a pull request merge, and could move a protected file out of the pattern's reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository's runners. Changed files are now listed unquoted, and a rename reports both the old and the new path. | ||||
| CVE-2026-125617 | 1 Gitea | 1 Gitea | 2026-11-16 | 4.3 Medium |
| `GET /api/v1/users/{username}/orgs/{org}/permissions` only checked that the organization is visible to the caller and then returned the named user's role in it. Any signed-in user could learn whether another user is an owner, admin or member of a public or limited organization, including for members who conceal their membership. The roles are now only returned to the user themselves, to members of the organization and to site administrators. | ||||
| CVE-2026-126338 | 1 Gitea | 1 Gitea | 2026-11-16 | 3.1 Low |
| Replying to a code review comment accepted a review ID that belongs to a different pull request, through the web form, the API and incoming mail replies. A signed-in user could reply on a pull request they can access with the ID of a review in a repository they cannot read, and the new comment was attached to that review and received the diff context of the commented lines. Replies are now only accepted for a review of the same pull request, and for a pending review only from its author. | ||||
| CVE-2026-128359 | 1 Gitea | 1 Gitea | 2026-11-16 | 5.4 Medium |
| When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged for new tokens, so applications that sign users in through Gitea kept them signed in. The token endpoint now refuses users who may not sign in, and token introspection reports their tokens as inactive. | ||||
| CVE-2026-129337 | 1 Gitea | 1 Gitea | 2026-11-16 | 5.3 Medium |
| Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created. | ||||
| CVE-2026-129525 | 1 Gitea | 1 Gitea | 2026-11-16 | 5.4 Medium |
| 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, subscriptions, tracked times and reactions), and list pull requests through the repository's issue search and milestone pages; the same applied in the other direction. These endpoints now check read access to the unit the item belongs to. The API endpoints were fixed in 28.2.0 and 28.3.0, the search and milestone pages in 28.4.0. | ||||