NetSight

Security Dashboard

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

Reset
80 matching advisories · page 2 of 3Index updated 6 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-58427 Gitea: Private org member list leaked via /members API endpoint — incomplete fix for PR #38145 go · gitea.dev 2026-07-21 high7.7 CVE-2026-58314 Two SSRF findings in Gitea 1.26.2 go · code.gitea.io/gitea 2026-07-21 high7.5 CVE-2026-58436 Gitea: ParseAcceptLanguage quadratic-time DoS via Locale middleware on unauthenticated requests go · code.gitea.io/gitea 2026-07-21 high7.1 CVE-2026-58437 Gitea: Repository Visibility Manipulation via Git Push Options go · code.gitea.io/gitea 2026-07-21 high8.1 CVE-2026-55987 Gitea: OAuth2 sign-in reactivates an administrator-deactivated account on auth sources without refresh tokens (incomplete fix of #38009) go · code.gitea.io/gitea 2026-07-21 high7.5 CVE-2026-58434 Gitea: Private Repository Metadata Remains Accessible After Access Revocation go · code.gitea.io/gitea 2026-07-21 high7.5 CVE-2026-54481 Internal API HTTP client hardcodes InsecureSkipVerify:true with no config override (CWE-295) go · code.gitea.io/gitea 2026-07-21 high7.5 CVE-2026-58417 Gitea: REST API exposes organization membership of private organizations to public go · gitea.dev 2026-07-21 high7.1 CVE-2026-58416 Gitea: Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard) go · gitea.dev 2026-07-21 high7.5 CVE-2026-58438 Gitea: Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access go · gitea.dev 2026-07-21 high7.1 CVE-2026-56755 Gitea: Denial of Service (CPU & Memory Exhaustion) via O(N^2) String Concatenation in Debian Package Upload go · code.gitea.io/gitea 2026-07-21 high8.1 CVE-2026-58439 Gitea: Branch Protection Bypass via PR Retargeting Preserves Stale `official` Approval Flag go · code.gitea.io/gitea 2026-07-21 high8.5 CVE-2026-57894 Gitea: Repository Migration Follows Git HTTP Redirects After URL Allow/Block Validation, Enabling Internal Git Repository Exfiltration go · code.gitea.io/gitea 2026-07-21 high8.9 CVE-2026-58424 Gitea: Permanent Fork PR Workflow Approval Gate Bypass go · code.gitea.io/gitea 2026-07-03 high7.7 CVE-2026-58423 Gitea: LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositories go · code.gitea.io/gitea 2026-07-03 high7.5 CVE-2026-58421 Gitea: Unauthenticated ReDoS via CODEOWNERS pattern matching allows denial of service go · code.gitea.io/gitea 2026-07-03 high7.5 CVE-2026-58419 Gitea: Notification API leaks private issue metadata after access revocation go · code.gitea.io/gitea 2026-07-03 high7.1 CVE-2026-28740 Gitea versions up to and including 1.26.2 allow Git LFS object reuse to authorize private source objects for users who have repository access but lack Code-uni… go · gitea.dev 2026-07-03 high7.5 CVE-2026-27779 Gitea versions before 1.25.5 accept malformed or injected forwarded-proto values when detecting public URLs, allowing spoofed canonical URL generation. go · code.gitea.io/gitea 2026-07-03 high8.8 CVE-2026-27775 Gitea 1.25.5 caches a branch-specific write-permission result across multiple refs in one pre-receive hook session, allowing a per-branch maintainer-edit grant… go · code.gitea.io/gitea 2026-07-03 high8.2 CVE-2026-27771 Gitea versions up to and including 1.26.1 have insufficient permission checks for Composer package source links, which can expose private or internal package s… go · code.gitea.io/gitea 2026-07-03 high7.5 CVE-2026-27660 Gitea versions before 1.25.5 allow draft release data or attachments to be accessed without the required write permission. go · code.gitea.io/gitea 2026-07-03 high7.5 CVE-2026-27657 Gitea versions before 1.25.5 allow a user to change another user's primary email address. go · code.gitea.io/gitea 2026-07-03 high7.5 CVE-2026-26307 Gitea versions before 1.25.5 do not enforce a timeout on git grep searches, allowing expensive searches to consume server resources. go · code.gitea.io/gitea 2026-07-03 high7.5 CVE-2026-25712 Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations. go · code.gitea.io/gitea 2026-07-03 high7.5 CVE-2026-25038 Gitea 1.26.2 allows unauthorized users to access labels of private organizations. go · code.gitea.io/gitea 2026-07-03 high7.5 CVE-2026-24690 Gitea versions before 1.25.5 have insufficient permission checks for updating or rebasing pull request branches. go · code.gitea.io/gitea 2026-07-03 high7.5 CVE-2026-24451 Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be… go · code.gitea.io/gitea 2026-07-03 high7.1 CVE-2026-20779 Gitea versions from 1.5.0 before 1.26.3 have a TOTP single-use enforcement defect that allows a valid TOTP code to be accepted more than once across web two-fa… go · code.gitea.io/gitea 2026-07-03 high8.7 CVE-2026-28737 Gitea versions from 1.25.0 before 1.26.0 allow stored cross-site scripting through the extensionsRequired field in glTF files rendered by the 3D file viewer. go · code.gitea.io/gitea 2026-06-17

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.