CVE tracker
417 subscribers
6.14K links
News monitoring: @irnewsagency

Main channel: @orgsecuritygate

Site: SecurityGate.org
Download Telegram
CVE-2026-129465 - Zr.Admin.NET commit af07ffc through eb9228a IDOR via /system/user/profile

CVE ID :CVE-2026-129465
Published : 15 Nov. 2026, 2.17 | 2 jam, 12 menit ago
Description :Zr.Admin.NET commit af07ffc through commit eb9228a contains an insecure direct object reference vulnerability in SysProfileController.UpdateProfile that allows any authenticated user to modify other accounts via UserId. Attackers can set the administrator's phone number to one they control, request an SMS code via /checkMobile, and log in through /PhoneLogin to take over the administrator account.
Severity: 8.8 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-129466 - Zr.Admin.NET commit 1845017 through eb9228a Missing Authorization via /system/Tasks/get

CVE ID :CVE-2026-129466
Published : 15 Nov. 2026, 2.17 | 2 jam, 12 menit ago
Description :Zr.Admin.NET commit 1845017 through commit eb9228a contains a missing authorization vulnerability in TasksController.Get that allows any logged-in user to read scheduled task details without the monitor:job permission. Attackers can obtain task ids from the unprotected /monitor/jobLog/list endpoint and retrieve job parameters, API URLs, cron expressions, and stored SQL statements.
Severity: 5.3 | MEDIUM
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-129360 - Linux Foundation Magma Obsidian REST operator.go authentication spoofing

CVE ID :CVE-2026-129360
Published : 15 Nov. 2026, 3.15 | 1 jam, 14 menit ago
Description :A weakness has been identified in Linux Foundation Magma up to 1.9.0. The impacted element is an unknown function of the file orc8r/cloud/go/services/obsidian/access/operator.go of the component Obsidian REST. Executing a manipulation of the argument X-Magma-Client-Cert-Serial can lead to authentication bypass by spoofing. The attack can be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.
Severity: 7.5 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-129357 - Linux Foundation Magma Host Middleware middleware.ts hostOrgMiddleware authorization

CVE ID :CVE-2026-129357
Published : 15 Nov. 2026, 3.16 | 1 jam, 13 menit ago
Description :A vulnerability was determined in Linux Foundation Magma up to 1.9.0. This issue affects the function hostOrgMiddleware of the file nms/server/host/middleware.ts of the component Host Middleware. This manipulation of the argument role causes missing authorization. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
Severity: 6.5 | MEDIUM
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-129358 - Linux Foundation Magma NMS routes.ts handleReact cross site scripting

CVE ID :CVE-2026-129358
Published : 15 Nov. 2026, 3.16 | 1 jam, 13 menit ago
Description :A vulnerability was identified in Linux Foundation Magma up to 1.9.0. Impacted is the function handleReact of the file nms/server/main/routes.ts of the component NMS. Such manipulation leads to cross site scripting. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
Severity: 3.3 | LOW
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-129359 - Linux Foundation Magma interceptors.go hard-coded credentials

CVE ID :CVE-2026-129359
Published : 15 Nov. 2026, 3.16 | 1 jam, 13 menit ago
Description :A security flaw has been discovered in Linux Foundation Magma up to 1.9.0. The affected element is an unknown function of the file orc8r/lib/go/registry/interceptors.go. Performing a manipulation results in hard-coded credentials. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Severity: 7.5 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-129091 - WordPress GrandPrix Core plugin <= 1.0 - Local File Inclusion vulnerability

CVE ID :CVE-2026-129091
Published : Nov. 15, 2026, 7:17 p.m. | 5 hours, 14 minutes ago
Description :Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mikado-Themes GrandPrix Core grandprix-core allows PHP Local File Inclusion.This issue affects GrandPrix Core: from n/a through 1.0.
Severity: 8.1 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-123006 - Gitea password hash disclosure through repository search

CVE ID :CVE-2026-123006
Published : Nov. 15, 2026, 9:16 p.m. | 3 hours, 15 minutes ago
Description :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 repository they can see that has a commit status. The response now contains only the state and target URL of the commit status.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-125423 - Gitea command execution through repository auto-initialization

CVE ID :CVE-2026-125423
Published : Nov. 15, 2026, 9:16 p.m. | 3 hours, 15 minutes ago
Description :A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so that writing the README followed a symbolic link and overwrote a server-side git hook, which runs commands as the Gitea system user. The initial commit is now built in a freshly initialized directory, and a new repository only becomes ready, and accepts pushes, once its initialization is complete.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-118389 - Gitea RubyGems compact index injection through package metadata

CVE ID :CVE-2026-118389
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :The RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contain newline characters. Because the compact index served to clients is line-based, a user who can publish a gem to an owner's registry could forge index entries, such as packages that do not exist or additional versions of an existing gem with dependencies of their choice. Clients that resolve gems from that registry could then be led to install attacker-chosen dependencies. Gems with such metadata are now rejected.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-118535 - Gitea scoped workflow trust kept after repository transfer

CVE ID :CVE-2026-118535
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to another owner. The new owner could then change the workflows in the transferred repository, and they kept running in the previous owner's repositories with access to their Actions secrets and job tokens. A transfer now removes the owner-level registrations of the repository, and registrations whose source repository no longer belongs to the registering owner are ignored.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-120725 - Gitea anonymous Git LFS access despite required sign-in

CVE ID :CVE-2026-120725
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :With `REQUIRE_SIGNIN_VIEW = true`, the Git LFS endpoints still answered unauthenticated requests for repositories that are not private. An anonymous client who knows the path of such a repository and the SHA-256 of an LFS object could download the object, and could use the batch endpoint to test whether an object exists. The Git LFS endpoints now require authentication when sign-in is required to view the instance.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-120729 - Gitea stored cross-site scripting in the issue reference popup

CVE ID :CVE-2026-120729
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-120991 - Gitea deletion of shared container blobs on rejected uploads

CVE ID :CVE-2026-120991
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-123002 - Gitea missing attempt limit for TOTP passcodes

CVE ID :CVE-2026-123002
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-123009 - Gitea base repository code disclosure through the web editor in forks

CVE ID :CVE-2026-123009
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-123065 - Gitea deletion of arbitrary attachment files through release edit

CVE ID :CVE-2026-123065
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :When a release was edited, the files of the attachments to remove were deleted by the identifiers submitted in the form rather than by the attachments verified to belong to the release. A user with write access to the releases of any repository, including their own, could submit a crafted identifier that resolves to the stored file of another attachment and delete it, provided they know that attachment's UUID. The attachment record stayed, so downloads of the affected issue, comment or release file failed. Release edits now only delete the files of attachments that belong to the release.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-123638 - Gitea protected file pattern bypass with quoted file names

CVE ID :CVE-2026-123638
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-123642 - Gitea pull request creation without pull request access through AGit

CVE ID :CVE-2026-123642
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-125617 - Gitea hidden organization membership disclosure through the permissions API

CVE ID :CVE-2026-125617
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :`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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-126338 - Gitea private diff disclosure through code comment replies

CVE ID :CVE-2026-126338
Published : Nov. 15, 2026, 10:17 p.m. | 2 hours, 14 minutes ago
Description :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.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...