NetSight

Security Dashboard

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

Reset
11 matching advisories · page 1 of 1Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 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 low3.5 CVE-2026-117649 The issue timeline API and the web issue page hid cross-reference events that point at issues the reader cannot access, but not "dependency added" and "depende… Gitea · Gitea 20 days ago low3.5 CVE-2026-60008 Gitea's Jupyter notebook renderer inserts the notebook's language_info.name metadata into a CSS class attribute while disabling sanitization and rendering dire… 38 days ago low2.7 CVE-2026-58511 Gitea: Webhook Authorization Header Returned in Plaintext via API go · code.gitea.io/gitea 2026-07-21 low2.7 CVE-2026-55984 Gitea: Null Pointer Dereference in AddTime API Causes Authenticated Denial of Service go · code.gitea.io/gitea 2026-07-21 low2.7 CVE-2026-58445 Gitea: Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API go · code.gitea.io/gitea 2026-07-21 low3.1 CVE-2026-23603 Gitea: Blind SSRF in OAuth2 avatar synchronization via unvalidated OIDC picture claim go · code.gitea.io/gitea 2026-07-21 low2.3 CVE-2026-0798 Gitea may send release notification emails for private repositories to users whose access has been revoked go · code.gitea.io/gitea 2026-01-22 low3.1 CVE-2025-68940 Gitea doesn't adequately enforce branch deletion permissions after merging a pull request. go · code.gitea.io/gitea 2025-12-26

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.