go CVE Vulnerabilities & Metrics

Focus on go vulnerabilities and metrics.

Last updated: 07 Jun 2025, 22:25 UTC

About go Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with go. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total go CVEs: 2
Earliest CVE date: 26 Feb 2025, 08:14 UTC
Latest CVE date: 26 Feb 2025, 08:14 UTC

Latest CVE reference: CVE-2025-22869

Rolling Stats

30-day Count (Rolling): 0
365-day Count (Rolling): 2

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): 0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical go CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 0.0

Max CVSS: 0

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range Count
0.0-3.9 2
4.0-6.9 0
7.0-8.9 0
9.0-10.0 0

CVSS Distribution Chart

Top 5 Highest CVSS go CVEs

These are the five CVEs with the highest CVSS scores for go, sorted by severity first and recency.

All CVEs for go

CVE-2025-22869 go vulnerability CVSS: 0 26 Feb 2025, 08:14 UTC

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

CVE-2025-22868 go vulnerability CVSS: 0 26 Feb 2025, 08:14 UTC

An attacker can pass a malicious malformed token which causes unexpected memory to be consumed during parsing.