NetSight

Security Dashboard

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

Reset
355 matching advisories · page 2 of 12Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2026-117649 The issue timeline API and the web issue page hid cross-reference events that point at issues the reader cannot access, but not "dependency added" and "depende… Gitea · Gitea 20 days ago medium4.3 CVE-2026-117646 The repositories, stars and watching tabs of user profiles and the repository list of organization home pages included private repositories for every signed-in… Gitea · Gitea 20 days ago medium6.5 CVE-2026-117635 The `/api/v1/admin` route group did not enforce the `public-only` restriction of personal access tokens. Gitea · Gitea 20 days ago medium6.5 CVE-2026-116474 The `GITEA_TOKEN` of a Gitea Actions job authenticates as the `gitea-actions` system user, and the `/api/v1/user` email and GPG key endpoints accepted that use… Gitea · Gitea 20 days ago medium6.5 CVE-2026-116296 The API routes for releases, release assets, milestones and repository labels did not reject changes to archived repositories. 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 medium5.3 CVE-2026-114199 `GET /api/v1/users/{username}/heatmap` computed the contribution heatmap with the repository access of the token owner and ignored the public-only restriction … Gitea · Gitea 20 days ago medium5.4 CVE-2026-113429 Legacy (v1 to v3) Actions artifact uploads stored the request's `Content-Encoding` header unchecked in the column that is served as the artifact's `Content-Typ… Gitea · Gitea 20 days ago medium4.3 CVE-2026-112887 Gitea Actions task tokens authenticate to the REST API as a shared system user with a negative ID, which repository, organization, project and key filters trea… 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 medium6.5 CVE-2026-118386 Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the revie… Gitea · Gitea 20 days ago medium6.5 CVE-2026-97859 Seven Gitea API routes under `/api/v1/users/{username}` (followers, following, following/{target}, starred, subscriptions, keys and gpg_keys) were registered w… 34 days ago medium6.5 CVE-2026-110324 The visibility check of Gitea user profiles was applied to GET requests only, while `POST /{username}` (follow and unfollow) required only a signed-in user. 34 days ago medium4.3 CVE-2026-107686 The Gitea web handlers for adding and removing reactions on issues and comments did not refuse locked issues for users without write access, although the API d… 34 days ago medium6.5 CVE-2026-105964 The Gitea Actions artifact v4 (Twirp) handlers read the whole request body into memory without a size limit. 34 days ago 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 high7.5 CVE-2026-109553 Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only principal keys. Gitea · Gitea 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 high8.1 CVE-2026-73804 Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account. 38 days ago high8.8 CVE-2026-73800 Gitea resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event. 38 days ago high7.5 CVE-2026-73539 Gitea substitutes a URL derived from the markup Context field into external renderer command templates without escaping the reference path before shell-style a… 38 days ago high8.8 CVE-2026-73535 Gitea's OpenID connect handler accepts a user's password without enforcing enrolled TOTP or WebAuthn verification before completing sign-in and linking an Open… 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 high8.8 CVE-2026-71184 Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the ru… 38 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.