NetSight

Security Dashboard

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

Reset
39 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.1 CVE-2026-133113 Gogs through 0.14.4 contains an authorization bypass vulnerability that allows collaborators with write access to push to protected branches by merging pull re… gogs · gogs 2 days ago high7.1 CVE-2026-123012 In Gogs 0.14.3, the Git Smart HTTP authorization layer in internal/route/repo/http.go allows a push when only read access was intended, a different vulnerabili… gogs · gogs, Gogs · Gogs 17 days ago high7.1 CVE-2026-52812 Gogs: LFS dedupe path leaks private repo content across tenants go · gogs.io/gogs 2026-06-23 high7.1 CVE-2026-52810 Gogs allows users to write to readonly repositories using receive-pack + service=git-upload-pack confusion go · gogs.io/gogs 2026-06-23 high7.1 CVE-2026-52808 Gogs's write-level collaborators can mutate admin-only repository settings via API go · gogs.io/gogs 2026-06-23 high8.7 CVE-2026-52805 Gogs has a Migration Redirect Bypass that Leads to Internal Repository Theft go · gogs.io/gogs 2026-06-23 high8.1 CVE-2026-52801 Gogs has the ability to import local repositories via Mirror Settings go · gogs.io/gogs 2026-06-23 high8.8 CVE-2026-52800 Gogs Vulnerable to CSRF Leading to Organization Owner Takeover go · gogs.io/gogs 2026-06-23 high7.5 CVE-2026-52799 Gogs Missing Authorization in Attachment Download go · gogs.io/gogs 2026-06-22 high8.9 CVE-2026-52798 Gogs is an open source self-hosted Git service. go · gogs.io/gogs 2026-06-22 high8.3 CVE-2026-47267 Gogs is an open source self-hosted Git service. go · gogs.io/gogs 2026-06-22 high7.7 CVE-2026-25119 Gogs has an Authentication Bypass via Unvalidated Reverse Proxy Headers go · gogs.io/gogs 2026-06-22 high8.5 GHSA-6vxv-wg6j-5qwp Gogs: XSS in .ipynb files renderer due to outdated notebookjs go · gogs.io/gogs 2026-06-19 high8.5 CVE-2026-52797 Gogs: Overwriting critical files results in a denial of service go · gogs.io/gogs 2026-06-16 high7.3 CVE-2026-26276 Gogs: DOM-based XSS via milestone selection go · gogs.io/gogs 2026-03-05 high8.8 CVE-2026-26194 Gogs: Release tag option injection in release deletion go · gogs.io/gogs 2026-03-05 high8.7 CVE-2026-26022 Gogs: Stored XSS via data URI in issue comments go · gogs.io/gogs 2026-03-05 high7.1 CVE-2026-25232 Gogs has a Protected Branch Deletion Bypass in Web Interface go · gogs.io/gogs 2026-02-17 high7.3 GHSA-26gq-grmh-6xm6 Gogs vulnerable to Stored XSS via Mermaid diagrams go · gogs.io/gogs 2026-02-06 high7.2 CVE-2026-24135 Gogs vulnerable to arbitrary file deletion via Path Traversal in wiki page update go · gogs.io/gogs 2026-02-06 high7.7 CVE-2025-64175 Gogs Vulnerable to 2FA Bypass via Recovery Code go · gogs.io/gogs 2026-02-06 high8.7 CVE-2025-8110 Gogs vulnerable to a bypass of CVE-2024-55947Exploited go · gogs.io/gogs 2025-12-10 high7.5 CVE-2025-59537 argo-cd vulnerable unauthenticated DoS via malformed Gogs webhook payload go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd/v3 2025-09-30 high8.8 CVE-2024-55947 Path Traversal in file update API in gogs go · gogs.io/gogs 2024-12-23 high8.8 CVE-2024-44625 Remote Code Execution in Gogs go · gogs.io/gogs 2024-11-15 high7.7 GHSA-8mm6-wmpp-mmm3 Duplicate Advisory: Gogs allows argument injection during the tagging of a new release go · github.com/gogs/gogs 2024-07-04 high7.7 CVE-2024-39933 Gogs allows argument Injection when tagging new releases go · gogs.io/gogs 2024-07-04 high8.1 CVE-2022-1993 Path Traversal in Git HTTP endpoints in Gogs go · gogs.io/gogs 2022-06-08 high8.3 CVE-2022-1285 Server-Side Request Forgery in gogs webhook go · gogs.io/gogs 2022-06-01 high8.8 CVE-2022-0415 Unrestricted Upload of File with Dangerous Type in Gogs go · gogs.io/gogs 2022-03-21

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.