NetSight

Security Dashboard

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

Reset
124 matching advisories · page 1 of 5Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 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 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 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 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 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 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 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 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 medium4.3 CVE-2026-117646 The repositories, stars and watching tabs of user profiles and the repository list of organization home pages included private repositories for every signed-in… Gitea · Gitea 20 days ago medium6.5 CVE-2026-117635 The `/api/v1/admin` route group did not enforce the `public-only` restriction of personal access tokens. Gitea · Gitea 20 days ago medium6.5 CVE-2026-116474 The `GITEA_TOKEN` of a Gitea Actions job authenticates as the `gitea-actions` system user, and the `/api/v1/user` email and GPG key endpoints accepted that use… Gitea · Gitea 20 days ago medium6.5 CVE-2026-116296 The API routes for releases, release assets, milestones and repository labels did not reject changes to archived repositories. Gitea · Gitea 20 days ago medium5.3 CVE-2026-114199 `GET /api/v1/users/{username}/heatmap` computed the contribution heatmap with the repository access of the token owner and ignored the public-only restriction … Gitea · Gitea 20 days ago medium5.4 CVE-2026-113429 Legacy (v1 to v3) Actions artifact uploads stored the request's `Content-Encoding` header unchecked in the column that is served as the artifact's `Content-Typ… Gitea · Gitea 20 days ago medium4.3 CVE-2026-112887 Gitea Actions task tokens authenticate to the REST API as a shared system user with a negative ID, which repository, organization, project and key filters trea… Gitea · Gitea 20 days ago medium6.5 CVE-2026-118386 Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the revie… Gitea · Gitea 20 days ago medium6.5 CVE-2026-97859 Seven Gitea API routes under `/api/v1/users/{username}` (followers, following, following/{target}, starred, subscriptions, keys and gpg_keys) were registered w… 34 days ago medium6.5 CVE-2026-110324 The visibility check of Gitea user profiles was applied to GET requests only, while `POST /{username}` (follow and unfollow) required only a signed-in user. 34 days ago medium4.3 CVE-2026-107686 The Gitea web handlers for adding and removing reactions on issues and comments did not refuse locked issues for users without write access, although the API d… 34 days ago medium6.5 CVE-2026-105964 The Gitea Actions artifact v4 (Twirp) handlers read the whole request body into memory without a size limit. 34 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.