An administrator may attempt to block all networks by specifying "\*" or "all" as the network identifier. However, these values are not supported and do not trigger any validation error. Instead, they are silently interpreted as network 0 which results in no networks being blocked at all.
CVE-2025-41759
MEDIUMPre-NVD 4.94.9—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 4.9 from GitHub Security Advisory published 2026-03-09. a secondary CVSS source baseline 4.9; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
4.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.9Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.9
- EG Score
- 4.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 computedSeverity49% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
March 9, 2026
Last Modified
June 17, 2026
References (1)
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× 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.
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:29 UTCEPSS rescore
- 2026-07-28 15:35 UTCEPSS rescore
- 2026-07-27 13:48 UTCEG score recompute
- 2026-07-27 13:48 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2025-41759?
CVE-2025-41759 is a medium vulnerability published on March 9, 2026. An administrator may attempt to block all networks by specifying "\*" or "all" as the network identifier. However, these values are not supported and do not trigger any validation error. Instead, they are silently interpreted as network 0 which results in no networks being blocked at all.
When was CVE-2025-41759 disclosed?
CVE-2025-41759 was first published in the National Vulnerability Database on March 9, 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-2025-41759 actively exploited?
CVE-2025-41759 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 75.5% of all scored CVEs.
What is the CVSS score of CVE-2025-41759?
CVE-2025-41759 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2025-41759?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-41759, 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-41759
Is Your Infrastructure Affected by CVE-2025-41759?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.