NetSight

Security Dashboard

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

Reset
124 matching advisories · page 2 of 5Index updated 10 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2026-104627 The Gitea OpenID association callback in the security settings accepted a positive OpenID 2.0 assertion without checking that the signed-in user had started th… 34 days ago medium5.9 CVE-2026-78433 Gitea's web attachment handler skips its cross-repository ownership check for attachments created before 16 January 2026 and checks permissions against the rep… 38 days ago medium5.3 CVE-2026-78231 When OpenID sign-in is enabled, Gitea processes unauthenticated assertion parameters and sends an HTTP POST request to the caller-supplied OpenID provider endp… 38 days ago medium6.5 CVE-2026-73814 Gitea's collaboration access-mode endpoint accepts the Owner access mode from an authenticated repository collaborator with Admin access. 38 days ago medium4.3 CVE-2026-73273 Gitea's Maven upload handler reads checksum uploads entirely into memory and returns before enforcing package-size quotas. 38 days ago medium5.3 CVE-2026-73135 Gitea uses inconsistent repository visibility predicates, and the condition used by some repository-listing endpoints admits repositories whose owners are hidd… 38 days ago medium4.3 CVE-2026-73130 Gitea does not limit the length of the gitignores field accepted by repository-creation forms and the API. 38 days ago medium4.3 CVE-2026-73126 Gitea's Actions workflow status badge endpoint does not enforce repository-read scope or the public-only restriction on the token authenticating the request. 38 days ago medium4.3 CVE-2026-71301 Gitea's repository markup endpoint resolves same-repository pull request references without enforcing the viewer's Pull Requests permission. 38 days ago medium4.3 CVE-2026-70407 Gitea's organization-list API does not enforce the read:organization token scope. 38 days ago medium6.5 CVE-2026-70406 Gitea's shared comparison helper omits the token repository-access check used when updating pull requests. 38 days ago medium5.8 CVE-2026-70402 Gitea creates server-side Git hook directories and scripts with mode 0777 and relies on the process umask to restrict access. 38 days ago medium5.4 CVE-2026-70400 Gitea's repository migration API accepts a public-only token when the request specifies creation of a private repository. 38 days ago medium5.4 CVE-2026-70396 Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation route… 38 days ago medium4.3 CVE-2026-68964 Gitea's user SSH and GPG key-list API endpoints omit the profile visibility check applied by their web equivalents. 38 days ago medium4.3 CVE-2026-68957 Gitea's API and web issue-search paths do not treat restricted accounts as anonymous viewers when evaluating Limited-visibility repository owners. 38 days ago medium4.3 CVE-2026-67577 Gitea's activity-feed and contribution-heatmap API handlers do not apply the profile visibility check for restricted accounts viewing Limited-visibility users. 38 days ago medium6.5 CVE-2026-66874 For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters … 38 days ago medium4.3 CVE-2026-66853 Gitea's user organization-list API includes Limited-visibility organizations for authenticated restricted accounts without applying the visibility restriction … 38 days ago medium4.3 CVE-2026-66849 Gitea's package registry grants authenticated users read access to packages owned by Limited-visibility users without excluding restricted accounts. 38 days ago medium5.3 CVE-2026-63792 Gitea's collaborative-owner authorization path for reading cross-repository reusable workflows does not exclude fork pull request runs. 38 days ago medium6.5 CVE-2026-63021 Gitea's Swift package parser limits each manifest to 128 KiB but does not limit the number of manifests or their aggregate size before reading them into memory. 38 days ago medium6.5 CVE-2026-62925 Gitea parses Alpine package uploads before enforcing package-size quotas and does not bound the decompressed .PKGINFO data or its dependency and provides entry… 38 days ago medium6.5 CVE-2026-60021 Gitea's initial GitLab migration version probe uses an HTTP client without a timeout and does not attach the migration task's cancellation context. 38 days ago medium6.5 CVE-2026-60018 Gitea's OneDev migration downloader reads the entire remote version response into memory without a size limit and uses a client without a timeout. 38 days ago medium6.5 CVE-2026-60010 Gitea's repository-side team-link API allows a repository administrator who is not an organization owner to attach organization teams to a repository despite R… 38 days ago medium5.3 CVE-2026-25946 When OpenID sign-in is enabled, Gitea accepts a user-supplied OpenID URL and performs discovery requests without validating the destination against internal ne… 38 days ago medium4.9 CVE-2026-97208 The Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mi… gitea · gitea 46 days ago medium6.1 CVE-2026-96594 The Gitea API endpoint `GET /api/v1/repos/{owner}/{repo}/media/{filepath}` wrote files of up to 1 KiB that are stored directly in Git, not in LFS, to the respo… gitea · gitea 46 days ago medium5.4 CVE-2026-89182 With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push opti… gitea · gitea 46 days ago

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.