CVE-2025-64175 - Vulnerability Details

Threat entity extracted from intelligence sources

Frequency
2
occurrences
First Seen
March 3, 2026
Last Seen
June 25, 2026

CVE-2025-64175 is a vulnerability tracked by ThreatCluster, appearing in 2 threat clusters built from 2 intelligence report mentions.

CVE-2025-64175 is a vulnerability tracked across 2 threat clusters and 2 intelligence report mentions on ThreatCluster. First observed March 3, 2026; most recent activity June 25, 2026.

Related Threat Clusters

Recent Intelligence Reports

  • Multiple Critical Vulnerability Disclosures Across Gogs, Jinjava, and Kubernetes Local Path ... — Mallory.Ai · June 25, 2026
  • openSUSE 15.6 Important Advisory govulncheck-vulndb Update ID 2026-0757 — Linuxsecurity · March 3, 2026

Frequently asked questions

What is CVE-2025-64175?

CVE-2025-64175 is a vulnerability tracked by ThreatCluster, appearing in 2 threat clusters built from 2 intelligence report mentions.

Is CVE-2025-64175 still active?

The most recent intelligence report mentioning CVE-2025-64175 on ThreatCluster is dated June 25, 2026. Activity was first observed March 3, 2026, giving a tracked span from then to June 25, 2026.

What is CVE-2025-64175 associated with?

Across ThreatCluster reporting, CVE-2025-64175 most frequently co-occurs with Gogs, OpenSUSE, CVE-2017-18873, CVE-2017-18903, CVE-2017-18906, among 12 tracked related entities.

What are the latest developments involving CVE-2025-64175?

The most significant recent cluster is “Critical Vulnerabilities in Gogs and Jinjava Require Immediate Patching” (2 articles · Updated June 25, 2026). CVE-2025-64175 appears across 2 threat clusters in total, listed above with sources.

How much reporting does ThreatCluster have on CVE-2025-64175?

CVE-2025-64175 appears in 2 intelligence report mentions across 2 deduplicated threat clusters, aggregated from 17,000+ monitored sources.

CVSS v3.1 Breakdown