NetSight

Security Dashboard

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

Reset
2,013 matching advisories · page 12 of 68Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
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-52792 Algernon vulnerable to server-side script source disclosure on Windows via NTFS filename go · github.com/xyproto/algernon 2026-07-02 high8.1 CVE-2026-44454 Coder vulnerable to workspace auto-creation via crafted URL parameters without user consent go · github.com/coder/coder/v2, go · github.com/coder/coder 2026-07-02 high8.1 CVE-2026-50138 goshs: WebDAV listener ignores --read-only, --upload-only, and --no-delete mode flags go · goshs.de/goshs/v2 2026-07-01 high7.1 CVE-2026-50163 `oras-go` tar extraction: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution go · oras.land/oras-go/v2 2026-07-01 high7.5 CVE-2026-50151 oras-go blob upload vulnerable to credential forwarding via unvalidated Location header go · oras.land/oras-go/v2 2026-07-01 high8.2 CVE-2026-44937 Potential forgery of webhook requests when using a unauthenticated webhook in SUSE Rancher Fleet 0.15 before 0.15.2, 0.14 before 0.14.6, 0.13 before 0.13.11 an… go · github.com/rancher/fleet 2026-07-01 high8.8 CVE-2026-44938 A vulnerability has been identified in Fleet's agent-side deployer, which did not filter security-sensitive keys from namespaceLabels in fleet.yaml (or BundleD… go · github.com/rancher/fleet 2026-07-01 high8.2 CVE-2026-49998 Centrifugo's dynamic JWKS key cache keyed only by `kid` allows cross-issuer JWT authentication bypass go · github.com/centrifugal/centrifugo/v6, go · github.com/centrifugal/centrifugo/v5, go · github.com/centrifugal/centrifugo/v4 +2 2026-07-01 high8.7 CVE-2026-49478 Fulcio has OIDC Discovery Redirect Following Allows SSRF and JWKS Substitution for Meta-Issuer Paths, with Kubernetes Service-Account Token Leakage go · github.com/sigstore/fulcio 2026-06-30 high8.1 GHSA-7m8x-qg2j-4m3v Fission: MessageQueueTrigger scaler manager materializes Secret values into Deployment envvars and accepts arbitrary user PodSpec go · github.com/fission/fission 2026-06-30 high GHSA-55f6-4pr5-c7m5 Kahi has privilege-drop and socket/log permission issues go · github.com/kahiteam/kahi 2026-06-30 high7.1 CVE-2026-58167 Nightingale (n9e) before 9.0.0-beta.2 exposes full datasource configurations, including plaintext database passwords, HTTP bearer tokens, HTTP basic-auth passw… go · github.com/ccfos/nightingale/v6 2026-06-30 high7.5 CVE-2026-53433 fzf is vulnerable to a Denial of Service (DoS) due to inefficient HTTP body processing in the --listen mode due to inefficient HTTP body processing using repea… go · github.com/junegunn/fzf 2026-06-30 high8.8 CVE-2026-41053 Incorrect authentication caching in the team member ship expansion of the Rancher Github authentication provider caused it granting principal access to any log… go · github.com/rancher/rancher 2026-06-30 high7.5 CVE-2026-44840 Dgraph Vulnerable to DQL Injection via checkUserPassword GraphQL Query go · github.com/dgraph-io/dgraph/v25 2026-06-29 high GHSA-wcr3-9x4c-f5gj Blnk has an API key authorization bypass in owner and scope enforcement go · github.com/blnkfinance/blnk 2026-06-26 high8.8 CVE-2026-49258 Nebula Mesh: Web UI lacks ownership checks, enabling cross-operator access to hosts and networks (read, block, delete) go · github.com/juev/nebula-mesh 2026-06-26 high7.5 GHSA-jqc5-2p7q-fqfc Hysteria: http large header with sniff cause server DoS go · github.com/apernet/hysteria 2026-06-26 high7.5 GHSA-qh5x-rfwf-rvfv Hysteria vulnerable to server crash when max_datagram_frame_size very small go · github.com/apernet/hysteria 2026-06-26 high7.4 GHSA-vgrc-hq28-p3xp Hysteria has an authenticated UDP ACL bypass that enables localhost and private-network UDP SSRF go · github.com/apernet/hysteria/core/v2 2026-06-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.