NetSight

Security Dashboard

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

Reset
124 matching advisories · page 4 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2026-27761 Gitea versions up to and including 1.26.2 allow repository RSS and Atom feed endpoints to bypass API access token scope checks, exposing private repository com… go · code.gitea.io/gitea 2026-07-03 medium5.3 CVE-2026-25782 Gitea versions before 1.25.5 look up tracked-time entries by time ID without scoping the lookup to the issue in the request URL, allowing deletion attempts to … go · code.gitea.io/gitea 2026-07-03 medium5.3 CVE-2026-20909 Gitea versions before 1.25.5 have insufficient permission checks when listing tracked time entries. go · code.gitea.io/gitea 2026-07-03 medium6.1 CVE-2026-25779 Gitea versions up to and including 1.25.4 allow redirect bypasses through raw or percent-encoded backslashes in redirect_to values. go · github.com/go-gitea/gitea 2026-06-17 medium4.3 CVE-2026-27783 Gitea versions up to and including 1.26.1 do not enforce repository-unit authorization on issue-template API endpoints. go · code.gitea.io/gitea 2026-06-16 medium4.3 CVE-2026-25714 Gitea versions up to and including 1.26.1 do not apply public-only token filtering consistently to the user organization API, leaving an incomplete fix for CVE… go · code.gitea.io/gitea 2026-06-16 medium6.3 GHSA-3m6q-h5gj-7mrw Gitea has insecure default SSH settings go · code.gitea.io/gitea 2026-04-22 medium5.3 CVE-2026-20904 Gitea does not properly validate ownership when toggling OpenID URI visibility go · github.com/go-gitea/gitea 2026-01-22 medium5.3 CVE-2026-20888 Gitea does not properly verify authorization when canceling scheduled auto-merges via the web interface go · github.com/go-gitea/gitea 2026-01-22 medium6.5 CVE-2026-20883 Gitea improperly exposes issue titles and repository names through previously started stopwatches go · github.com/go-gitea/gitea 2026-01-22 medium6.5 CVE-2026-20800 Gitea improperly exposes issue and pull request titles go · github.com/go-gitea/gitea 2026-01-22 medium5.3 CVE-2025-69413 Gitea's /api/v1/user endpoint has different responses for failed authentication depending on whether a username exists go · code.gitea.io/gitea 2026-01-01 medium5.4 CVE-2025-68946 Gitea vulnerable to Cross-site Scripting go · code.gitea.io/gitea 2025-12-26 medium5.8 CVE-2025-68945 Gitea: anonymous user can visit private user's project go · code.gitea.io/gitea 2025-12-26 medium5.0 CVE-2025-68944 Gitea sometimes mishandles propagation of token scope for access control within one of its own package registries go · code.gitea.io/gitea 2025-12-26 medium5.3 CVE-2025-68943 Gitea inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order go · code.gitea.io/gitea 2025-12-26 medium5.4 CVE-2025-68942 Gitea allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text go · code.gitea.io/gitea 2025-12-26 medium4.9 CVE-2025-68941 Gitea mishandles access to a private resource upon receiving an API token with scope limited to public resources go · code.gitea.io/gitea 2025-12-26 medium4.3 CVE-2025-68938 Gitea mishandles authorization for deletion of releases go · code.gitea.io/gitea 2025-12-26 medium6.5 CVE-2022-38795 Gitea erroneous repo clones go · code.gitea.io/gitea 2023-08-07 medium4.4 CVE-2023-3515 code.gitea.io/gitea Open Redirect vulnerability go · code.gitea.io/gitea 2023-07-05 medium4.3 CVE-2022-46685 Jenkins Gitea Plugin vulnerable to Cleartext Transmission of Sensitive Information maven · org.jenkins-ci.plugins:gitea 2022-12-12 medium6.5 CVE-2022-38183 Gitea allowed assignment of private issues go · code.gitea.io/gitea 2022-08-12 medium4.4 CVE-2022-1928 Stored Cross-site Scripting in gitea go · code.gitea.io/gitea 2022-05-29 medium6.1 CVE-2022-1058 Gitea Open Redirect go · code.gitea.io/gitea 2022-03-24 medium5.3 CVE-2021-29134 Path Traversal in Gitea go · code.gitea.io/gitea 2022-03-15 medium6.1 CVE-2021-45329 Cross-site Scripting in Gitea go · github.com/go-gitea/gitea 2022-02-08 medium6.1 CVE-2021-45328 Open redirect in Gitea go · github.com/go-gitea/gitea 2022-02-08 medium6.5 CVE-2021-39867 In all versions of GitLab CE/EE since version 8.15, a DNS rebinding vulnerability in Gitea Importer may be exploited by an attacker to trigger Server Side Requ… gitlab · gitlab 2021-10-05 medium5.4 CVE-2021-28378 Cross-site Scripting in Gitea go · code.gitea.io/gitea 2021-03-15

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.