NetSight

Security Dashboard

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

Reset
124 matching advisories · page 3 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2026-105268 The Gitea API routes for issue attachments (`/api/v1/repos/{owner}/{repo}/issues/{index}/assets/{attachment_id}`) also accepted attachments that belong to comm… gitea · gitea 46 days ago medium6.5 CVE-2026-104633 When migrating a repository from another Gitea instance, Gitea used the page size reported in the source server's API settings to end its paginated downloads. gitea · gitea 46 days ago medium4.3 CVE-2026-96589 When a private repository is transferred to a user who lacks access, Gitea grants that recipient temporary read access as a collaborator so they can review the… gitea · gitea 46 days ago medium4.3 CVE-2026-96400 With `[migrations] ALLOWED_DOMAINS` set to a matching entry such as `*` or a hostname wildcard, Gitea's migration URL validation could permit reserved and link… gitea · gitea 46 days ago medium6.5 CVE-2026-95112 When processing issue and comment bodies, Gitea scanned the entire preceding text for action keywords such as "closes" or "fixes" once per Markdown link, givin… gitea · gitea 46 days ago medium5.4 CVE-2026-103667 Gitea's container registry served blob downloads with a `Content-Type` taken from the media type declared in pushed image manifests, without a `Content-Disposi… gitea · gitea 46 days ago medium4.3 CVE-2026-101029 Gitea's repository migration and pull mirror egress checks could be bypassed with a hostname that returns multiple DNS answers, because the address that was va… gitea · gitea 46 days ago medium4.9 CVE-2026-58429 Gitea: Public-Only Personal access tokens scope bypass in Organization and Permission Endpoints go · code.gitea.io/gitea 2026-07-21 medium6.5 CVE-2026-57897 Gitea: Cross-Repo Information Disclosure via Org-Level Actions Run/Job APIs go · code.gitea.io/gitea 2026-07-21 medium4.3 CVE-2026-58510 Gitea: GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private go · code.gitea.io/gitea 2026-07-21 medium4.3 CVE-2026-58431 Gitea: Public-only API token restriction is not enforced on team API routes go · gitea.dev 2026-07-21 medium6.2 CVE-2026-56657 Gitea SSH Key Parser Denial of Service go · code.gitea.io/gitea, go · gitea.dev 2026-07-21 medium5.4 CVE-2026-58435 Gitea LFS Deploy-Key Privilege Escalation go · code.gitea.io/gitea 2026-07-21 medium4.4 CVE-2026-58420 Gitea: Local File Inclusion via file:// URI in Migration Restore go · gitea.dev 2026-07-21 medium4.3 CVE-2026-50105 Gitea: RSS/Atom feed handlers bypass API-token scope & public-only confinement (incomplete fix of #37698) go · code.gitea.io/gitea 2026-07-21 medium6.5 CVE-2026-42931 Gitea: Denial of Service via Unbounded io.ReadAll in NPM Package Tag Endpoint go · code.gitea.io/gitea 2026-07-21 medium4.3 CVE-2026-58444 Gitea: Personal access token scope enforcement bypass on the repository home page (`GET /{owner}/{repo}`) discloses private repository contents go · code.gitea.io/gitea 2026-07-21 medium6.5 CVE-2026-58442 Gitea: Repository migration SSRF via multi-answer DNS allow-list bypass go · code.gitea.io/gitea 2026-07-21 medium6.3 CVE-2026-58441 Gitea: SSRF in restore-repo via unsanitized pull_request.yml Head.CloneURL go · code.gitea.io/gitea 2026-07-21 medium5.3 GHSA-rjvx-x5h2-6px5 Gitea: API Fork Endpoint Authorization Bypass Allows Organization Members to Bypass Repository Creation Restrictions go · code.gitea.io/gitea 2026-07-21 medium5.3 CVE-2026-58507 Gitea: Private Repository Existence Disclosure via go-get Meta Endpoint go · code.gitea.io/gitea 2026-07-21 medium5.9 CVE-2026-57886 Gitea: Cross-repository issue/comment attachment re-linking can expose private attachment content go · code.gitea.io/gitea 2026-07-21 medium4.3 CVE-2026-58425 Gitea: OAuth token introspection returns metadata of tokens issued to other clients (RFC 7662 section 4 violation) go · code.gitea.io/gitea 2026-07-21 medium4.3 CVE-2026-59763 Gitea: Unbounded Arch package file metadata can cause resource amplification in Gitea package uploads go · code.gitea.io/gitea 2026-07-21 medium5.9 CVE-2026-58432 Missing Authorization and Authorization Bypass Through User-Controlled Key and Incorrect Permission Assignment for Critical Resource and Exposure of Sensitive … go · code.gitea.io/gitea 2026-07-21 medium6.5 CVE-2026-58428 Gitea: Release attachment extension allowlist bypass via web release edit form (variant of CVE-2025-68939) go · code.gitea.io/gitea 2026-07-21 medium4.3 CVE-2026-59766 Gitea CVE-2026-20800 sibling endpoints not covered: revoked user still reads private repo objects via `/api/v1/user/starred` and private issue titles via `/api/v1/user/times` go · code.gitea.io/gitea 2026-07-21 medium6.8 CVE-2026-58440 Webhooks created by a collaborator keep firing after their repo access is revoked → ongoing real-time exfiltration of private repo content (incomplete revocati… go · gitea.dev 2026-07-21 medium6.5 CVE-2026-58418 Gitea: SSRF via HTTP Redirect in Repository Migration go · code.gitea.io/gitea 2026-07-03 medium5.3 CVE-2026-28705 Gitea versions before 1.25.5 use release tag names and asset names as filesystem path components when dumping release assets, allowing specially crafted names … go · code.gitea.io/gitea 2026-07-03

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.