CVE-2026-3579

MEDIUMNVD 5.95.9
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory (severity: LOW) published 2026-03-19. the CNA's CVSS baseline 2.1; sources differ by 3.8.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:wolfssl, ghsa
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

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

wolfSSL 5.8.4 on RISC-V RV32I architectures lacks a constant-time software implementation for 64-bit multiplication. The compiler-inserted __muldi3 subroutine executes in variable time based on operand values. This affects multiple SP math functions (sp_256_mul_9, sp_256_sqr_9, etc.), leading to a timing side-channel that may expose sensitive cryptographic data.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
27(Track)
EG Risk 27/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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

March 19, 2026

Last Modified

June 17, 2026

References (1)

Vendor Advisories for CVE-2026-3579(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 3× in last 7d / 3× 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-27 14:13 UTCEPSS rescore
  2. 2026-07-27 12:51 UTCEG score recompute
  3. 2026-07-27 12:51 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-3579?
CVE-2026-3579 is a medium vulnerability published on March 19, 2026. wolfSSL 5.8.4 on RISC-V RV32I architectures lacks a constant-time software implementation for 64-bit multiplication. The compiler-inserted muldi3 subroutine executes in variable time based on operand values. This affects multiple SP math functions (sp256mul9, sp256sqr9, etc.), leading to a timing…
When was CVE-2026-3579 disclosed?
CVE-2026-3579 was first published in the National Vulnerability Database on March 19, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3579 actively exploited?
CVE-2026-3579 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 81.8% of all scored CVEs.
What is the CVSS score of CVE-2026-3579?
CVE-2026-3579 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-3579?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3579, 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-2026-3579

Explore →

Is Your Infrastructure Affected by CVE-2026-3579?

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