NetSight

Security Dashboard

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

Reset
355 matching advisories · page 7 of 12Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 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 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 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 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 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 high8.7 CVE-2026-28737 Gitea versions from 1.25.0 before 1.26.0 allow stored cross-site scripting through the extensionsRequired field in glTF files rendered by the 3D file viewer. go · code.gitea.io/gitea 2026-06-17 high8.1 CVE-2026-24791 Gitea: Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes go · code.gitea.io/gitea 2026-06-17 high8.1 CVE-2026-22555 Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organ… go · code.gitea.io/gitea 2026-06-17 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 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 high8.5 CVE-2026-26231 Gitea versions up to and including 1.26.1 allow the Allow edits from maintainers permission path to authorize commits to repositories that the user can read bu… go · code.gitea.io/gitea 2026-06-16 high8.1 CVE-2026-28699 Gitea versions up to and including 1.26.1 allow OAuth2 access token scope enforcement to be bypassed through HTTP Basic authentication. go · code.gitea.io/gitea 2026-06-16 high8.1 CVE-2026-28744 Gitea versions up to and including 1.26.1 allow Git smart HTTP requests authenticated with bearer tokens to bypass repository token scope checks. 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 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 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 critical9.1 CVE-2026-20897 Gitea does not properly validate repository ownership when deleting Git LFS locks 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 critical9.1 CVE-2026-20750 Gitea does not properly validate project ownership in organization project operations go · github.com/go-gitea/gitea 2026-01-22 high7.5 CVE-2026-20736 Gitea has improper access control for uploaded attachments go · code.gitea.io/gitea 2026-01-22 low2.3 CVE-2026-0798 Gitea may send release notification emails for private repositories to users whose access has been revoked go · code.gitea.io/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

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.