NetSight

Security Dashboard

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

Reset
355 matching advisories · page 4 of 12Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-96580 Gitea expanded a workflow's static `strategy.matrix` into its full Cartesian product without a size limit when creating a run, before the fork pull request app… gitea · gitea 46 days ago high8.1 CVE-2026-96404 When Gitea's web installer is reachable against a database that already contains users, such as after `INSTALL_LOCK` has been reset to `false`, submitting the … gitea · gitea 46 days ago medium4.3 CVE-2026-96400 With `[migrations] ALLOWED_DOMAINS` set to a matching entry such as `*` or a hostname wildcard, Gitea's migration URL validation could permit reserved and link… gitea · gitea 46 days ago high7.5 CVE-2026-96399 A repository's external issue tracker regular expression containing alternating capture groups could produce invalid slice indexes when Gitea rendered issue re… gitea · gitea 46 days ago medium6.5 CVE-2026-95112 When processing issue and comment bodies, Gitea scanned the entire preceding text for action keywords such as "closes" or "fixes" once per Markdown link, givin… gitea · gitea 46 days ago critical9.1 CVE-2026-95106 Gitea accepted pushed Git trees containing two entries with the same name, which Git's own consistency checks reject. gitea · gitea 46 days ago critical9.8 CVE-2026-94205 Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. gitea · gitea 46 days ago high8.1 CVE-2026-89430 Gitea validated a push mirror's remote address against the `[migrations]` allow and block lists only when the mirror was created. gitea · gitea 46 days ago high7.1 CVE-2026-79960 When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated th… gitea · gitea 46 days ago critical9.8 CVE-2026-73278 Gitea's OAuth2 and OpenID Connect sign-in paths do not require a WebAuthn challenge when WebAuthn is the account's only configured second factor. gitea · gitea 46 days ago high7.5 CVE-2026-70357 Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves th… gitea · gitea 46 days ago high7.5 CVE-2026-104636 Gitea validated the initial remote URL for push mirrors, wiki remote checks, and fetches of migrated pull request heads, but the subsequent raw Git operations … gitea · gitea 46 days ago high8.8 CVE-2026-104632 Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. gitea · gitea 46 days ago high8.8 CVE-2026-104626 A user who can open a fork pull request can place workflow content with a shared run-level concurrency group into a Gitea Actions run that is awaiting approval. gitea · gitea 46 days ago high7.5 CVE-2026-103670 When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed… gitea · gitea 46 days ago medium5.4 CVE-2026-103667 Gitea's container registry served blob downloads with a `Content-Type` taken from the media type declared in pushed image manifests, without a `Content-Disposi… gitea · gitea 46 days ago critical9.1 CVE-2026-103059 When Gitea's built-in SSH server is enabled (`START_SSH_SERVER = true`), the presented public key was looked up with an SQL `LIKE` comparison of its encoded co… gitea · gitea 46 days ago medium4.3 CVE-2026-101029 Gitea's repository migration and pull mirror egress checks could be bypassed with a hostname that returns multiple DNS answers, because the address that was va… gitea · gitea 46 days ago high7.7 CVE-2026-101027 When `[migrations] ALLOWED_DOMAINS` was configured, a hostname matching the allow list was accepted without checking its resolved address against the local-net… gitea · gitea 46 days ago critical9.9 CVE-2026-73802 gitea-runner: workflow container.options passes host namespaces and capability flags to job container when privileged mode is disabled go · gitea.com/gitea/runner 50 days ago critical9.8 CVE-2026-60004 Gitea: Remote Code Execution via diffpatch Git Hook InstallationExploited go · gitea.dev 2026-08-25 critical9.1 CVE-2026-58508 Two SSRF vulnerabilities in Gitea migration/mirror (DNS rebinding + missing re-validation) 2026-08-13 high8.3 CVE-2026-34966 Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fe… Gitea · Gitea 2026-08-05 medium4.9 CVE-2026-58429 Gitea: Public-Only Personal access tokens scope bypass in Organization and Permission Endpoints go · code.gitea.io/gitea 2026-07-21 high7.5 CVE-2026-59765 Gitea: SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata go · code.gitea.io/gitea, go · gitea.dev 2026-07-21 low2.7 CVE-2026-58511 Gitea: Webhook Authorization Header Returned in Plaintext via API go · code.gitea.io/gitea 2026-07-21 medium6.5 CVE-2026-57897 Gitea: Cross-Repo Information Disclosure via Org-Level Actions Run/Job APIs go · code.gitea.io/gitea 2026-07-21 medium4.3 CVE-2026-58510 Gitea: GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private go · code.gitea.io/gitea 2026-07-21 medium4.3 CVE-2026-58431 Gitea: Public-only API token restriction is not enforced on team API routes go · gitea.dev 2026-07-21 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

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.