NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
355 matching advisories · page 1 of 12Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.3 CVE-2026-129880 DeepAudit 2.0.0-beta.5 through 3.8.0 contains a server-side request forgery vulnerability that allows registered users to leak server-wide GitLab or Gitea toke… lintsinghua · DeepAudit 5 days ago medium5.4 CVE-2026-129525 Several endpoints that work on both issues and pull requests did not check which of the two the addressed item is. Gitea · Gitea 6 days ago medium5.4 CVE-2026-129341 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 reacha… Gitea · Gitea 6 days ago medium5.3 CVE-2026-129337 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 enforc… Gitea · Gitea 6 days ago low3.1 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… Gitea · Gitea 6 days ago medium5.4 CVE-2026-128359 When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. Gitea · Gitea 6 days ago medium5.3 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 … Gitea · Gitea 6 days ago low3.1 CVE-2026-126338 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. Gitea · Gitea 6 days ago medium4.3 CVE-2026-125617 `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. Gitea · Gitea 6 days ago medium4.3 CVE-2026-123642 The AGit flow (pushing to `refs/for/...`) did not check the pusher's access to pull requests again when it created the pull request. Gitea · Gitea 6 days ago high8.3 CVE-2026-123638 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… Gitea · Gitea 6 days ago medium5.7 CVE-2026-123065 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… Gitea · Gitea 6 days ago medium4.3 CVE-2026-123009 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. Gitea · Gitea 6 days ago high7.5 CVE-2026-123002 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` heade… Gitea · Gitea 6 days ago medium6.5 CVE-2026-120991 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 con… Gitea · Gitea 6 days ago medium5.4 CVE-2026-120729 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. Gitea · Gitea 6 days ago low3.7 CVE-2026-120725 With `REQUIRE_SIGNIN_VIEW = true`, the Git LFS endpoints still answered unauthenticated requests for repositories that are not private. Gitea · Gitea 6 days ago medium5.5 CVE-2026-118535 A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to another owner. Gitea · Gitea 6 days ago high8.8 CVE-2026-118389 The RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contain newline characters. Gitea · Gitea 6 days ago high8.8 CVE-2026-125423 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 repo… Gitea · Gitea 6 days ago medium6.5 CVE-2026-123006 The repository search used by the dashboard (`GET /repo/search`) returned the internal commit status object of each repository. Gitea · Gitea 6 days ago medium4.3 CVE-2026-119627 The web profile and RSS/Atom feed routes of users and organizations checked only whether a signed-in viewer could see a limited-visibility owner, without consi… Gitea · Gitea 20 days ago medium4.3 CVE-2026-119625 The `/{username}` web route accepted personal access tokens over HTTP Basic authentication without checking their scope. Gitea · Gitea 20 days ago high7.5 CVE-2026-119533 Repository and organization project boards listed the pull requests that reference each issue on the board without checking whether the viewer can read them. Gitea · Gitea 20 days ago high7.5 CVE-2026-119441 `DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route o… Gitea · Gitea 20 days ago medium6.5 CVE-2026-118504 The web interface blocks issue and pull request changes on archived repositories, but several issue routes of the REST API did not check whether the repository… Gitea · Gitea 20 days ago high7.5 CVE-2026-118395 Gitea 1.27.3 stopped personal access tokens restricted to public resources (`public-only`) from creating repositories through `POST /api/v1/user/repos` and `PO… Gitea · Gitea 20 days ago medium4.3 CVE-2026-118394 The OAuth2 userinfo endpoint (`/login/oauth/userinfo`) decided whether to limit the `groups` claim to public organizations by re-parsing the `Authorization` he… Gitea · Gitea 20 days ago critical9.1 CVE-2026-117685 The OCI registry's cross-repository blob mount checked the target package against the token's `public-only` restriction, but checked the source blob only again… Gitea · Gitea 20 days ago medium6.5 CVE-2026-117677 When parsing an uploaded Helm chart, Gitea decompressed the archive and read every tar entry while looking for `Chart.yaml` without limiting the decompressed s… Gitea · Gitea 20 days ago

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.