CVE-2025-63913

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered in OpenSBI 1.3 allowing attackers to cause a denial of service via crafted request to the SBI function #2 or the 'Find and configure a matching counter' function of SBI PMU extension.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

July 27, 2026

Last Modified

July 28, 2026

Advisory Details (1)

Auto-updated Jul 28, 2026
No patch confirmed yet.
generic

GitHub - luojia65/opensbi-pmu2-crash: RISC-V OpenSBI PMU #2 vulnerbility · GitHub

https://github.com/luojia65/opensbi-pmu2-crash

Vendor Advisories for CVE-2025-63913(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-30 02:31 UTCEG score recompute
  2. 2026-07-30 02:31 UTCGHSA enrichment
  3. 2026-07-30 01:30 UTCEPSS rescore
  4. 2026-07-29 14:33 UTCGHSA enrichment
  5. 2026-07-29 02:35 UTCEG score recompute
  6. 2026-07-29 02:35 UTCGHSA enrichment
  7. 2026-07-28 15:35 UTCEPSS rescore
  8. 2026-07-28 14:37 UTCGHSA enrichment
  9. 2026-07-28 13:44 UTCEG score recompute▲ 7.50
  10. 2026-07-28 13:44 UTCGHSA enrichment
  11. 2026-07-28 13:43 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  12. 2026-07-27 23:18 UTCNVD update
  13. 2026-07-27 22:41 UTCEG score recompute
  14. 2026-07-27 22:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-63913?
CVE-2025-63913 is a high vulnerability published on July 27, 2026. An issue was discovered in OpenSBI 1.3 allowing attackers to cause a denial of service via crafted request to the SBI function #2 or the 'Find and configure a matching counter' function of SBI PMU extension.
When was CVE-2025-63913 disclosed?
CVE-2025-63913 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-63913 actively exploited?
CVE-2025-63913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.0% of all scored CVEs.
What is the CVSS score of CVE-2025-63913?
CVE-2025-63913 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-63913?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-63913, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-63913

Explore →

Is Your Infrastructure Affected by CVE-2025-63913?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs