NetSight

Security Dashboard

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

Reset
140 matching advisories · page 1 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.1 CVE-2026-117685 The OCI registry's cross-repository blob mount checked the target package against the token's `public-only` restriction, but checked the source blob only again… Gitea · Gitea 20 days ago critical9.1 CVE-2026-116289 Gitea did not reject personal access tokens restricted to public resources (`public-only`) on the organization Actions runner registration-token endpoint, and … Gitea · Gitea 20 days ago critical9.8 CVE-2026-120263 When `[oauth2_client].ACCOUNT_LINKING` is set to `auto` (not the default) and registration is enabled, the link-account sign-up form looked up the existing acc… Gitea · Gitea 20 days ago critical9.8 CVE-2026-59774 Gitea's Org-mode markup renderer processes INCLUDE directives supplied to the repository markup endpoint without preventing access to server-side files. 38 days ago critical9.1 CVE-2026-101023 Gitea's OAuth2 token endpoint verified the signature and grant of a token submitted with the `refresh_token` grant type, but not that the token was a refresh t… 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 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 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 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 critical9.1 CVE-2026-55982 Gitea: OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes go · code.gitea.io/gitea 2026-07-21 critical9.1 CVE-2026-58443 Gitea: Public-only repository tokens can update private PR head branches go · code.gitea.io/gitea 2026-07-21 critical9.8 CVE-2026-56654 Gitea: Privilege Escalation via Access Token Scope Escalation in API go · code.gitea.io/gitea 2026-07-21 critical9.1 CVE-2026-56750 Gitea Remember-Me Token Theft Not Invalidating Attacker Session go · code.gitea.io/gitea 2026-07-21 critical9.6 CVE-2026-56443 Gitea: Token public-only scope bypassed on Limited-visibility owners (Repository + Package categories) — residual after CVE-2026-25714 / PR #37118 go · code.gitea.io/gitea, go · gitea.dev 2026-07-21 critical9.6 CVE-2026-58426 Gitea Actions Artifacts V4 signed URL HMAC ambiguity allows cross-repository artifact read and cross-task upload-state write go · code.gitea.io/gitea 2026-07-03 critical9.8 CVE-2026-58422 Gitea: Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts go · code.gitea.io/gitea 2026-07-03 critical9.8 CVE-2026-27780 Gitea versions before 1.26.0 do not fail closed on bufio.Scanner errors while processing pre-receive hook input, allowing oversized input to bypass branch-prot… go · code.gitea.io/gitea 2026-07-03 critical9.8 CVE-2026-26292 Gitea versions before 1.25.5 do not use the migration HTTP transport for LFS push and sync mirror operations, bypassing the configured migration transport prot… go · code.gitea.io/gitea 2026-07-03 critical9.1 CVE-2026-26247 Gitea versions before 1.25.5 do not persist the OAuth2 PKCE S256 challenge method correctly during authorization, allowing token exchange without the expected … go · code.gitea.io/gitea 2026-07-03 critical9.1 CVE-2026-26232 Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange. go · code.gitea.io/gitea 2026-07-03 critical9.1 CVE-2026-25718 Gitea versions before 1.25.5 mishandle path resolution during template repository generation, allowing template processing to read or write through symlinked o… go · code.gitea.io/gitea 2026-07-03 critical9.6 CVE-2026-22874 Gitea versions up to and including 1.26.2 have incomplete SSRF protection in webhook and migration allow-list filtering. go · code.gitea.io/gitea 2026-07-03 critical9.1 CVE-2026-22547 Gitea versions before 1.25.5 lack validation constraints for repository creation fields, including length-limited template fields and trust model or object for… go · code.gitea.io/gitea 2026-07-03 critical9.8 CVE-2026-20896 Gitea Docker image versions up to and including 1.26.2 use REVERSE_PROXY_TRUSTED_PROXIES=* by default, allowing any source IP to impersonate a user when revers… go · code.gitea.io/gitea 2026-07-03 critical9.9 CVE-2026-58053 Gitea act_runner with the Docker backend (through act 0.262.0) passes a workflow's container.options string to the Docker job container's HostConfig and, when … 2026-06-28 critical9.1 CVE-2026-20706 Gitea versions up to and including 1.26.1 allow repository archive downloads to bypass token scope checks on the web archive download endpoint. go · code.gitea.io/gitea 2026-06-16 critical9.1 CVE-2026-20912 Gitea does not properly validate repository ownership when linking attachments to releases go · github.com/go-gitea/gitea 2026-01-22

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.