CVE-2025-29779

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

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

Post-Quantum Secure Feldman's Verifiable Secret Sharing provides a Python implementation of Feldman's Verifiable Secret Sharing (VSS) scheme. In versions 0.8.0b2 and prior, the secure_redundant_execution function in feldman_vss.py attempts to mitigate fault injection attacks by executing a function multiple times and comparing results. However, several critical weaknesses exist. Python's execution environment cannot guarantee true isolation between redundant executions, the constant-time comparison implementation in Python is subject to timing variations, the randomized execution order and timing provide insufficient protection against sophisticated fault attacks, and the error handling may leak timing information about partial execution results. These limitations make the protection ineffective against targeted fault injection attacks, especially from attackers with physical access to the hardware. A successful fault injection attack could allow an attacker to bypass the redundancy check mechanisms, extract secret polynomial coefficients during share generation or verification, force the acceptance of invalid shares during verification, and/or manipulate the commitment verification process to accept fraudulent commitments. This undermines the core security guarantees of the Verifiable Secret Sharing scheme. As of time of publication, no patched versions of Post-Quantum Secure Feldman's Verifiable Secret Sharing exist, but other mitigations are available. Long-term remediation requires reimplementing the security-critical functions in a lower-level language like Rust. Short-term mitigations include deploying the software in environments with physical security controls, increasing the redundancy count (from 5 to a higher number) by modifying the source code, adding external verification of cryptographic operations when possible, considering using hardware security modules (HSMs) for key operations.

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

Published

March 14, 2025

Last Modified

April 15, 2026

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipPostQuantum-Feldman-VSSghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
postquantum-feldman-vss0.7.5b0, 0.7.6b0, 0.8.0b2

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 45× 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.

Showing the most recent 100 of 133 total refreshes for this CVE.

  1. 2026-07-26 14:53 UTCEPSS rescore
  2. 2026-07-25 14:17 UTCEPSS rescore
  3. 2026-07-24 14:17 UTCEPSS rescore
  4. 2026-07-23 02:52 UTCEG score recompute
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-22 14:07 UTCEPSS rescore
  7. 2026-07-21 15:24 UTCEPSS rescore
  8. 2026-07-21 15:24 UTCEPSS rescore
  9. 2026-07-20 17:07 UTCEPSS rescore
  10. 2026-07-19 14:30 UTCEPSS rescore
  11. 2026-07-19 14:30 UTCEPSS rescore
  12. 2026-07-19 02:28 UTCEPSS rescore
  13. 2026-07-19 02:28 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-16 17:02 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 01:59 UTCEPSS rescore
  20. 2026-07-15 01:59 UTCEPSS rescore
  21. 2026-07-14 08:25 UTCOSV refresh
  22. 2026-07-13 22:29 UTCEPSS rescore
  23. 2026-07-13 06:12 UTCEPSS rescore
  24. 2026-07-13 06:12 UTCEPSS rescore
  25. 2026-07-12 05:46 UTCEPSS rescore
Show 75 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-09 19:09 UTCEPSS rescore
  5. 2026-07-08 15:14 UTCEPSS rescore
  6. 2026-07-07 13:45 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 16:26 UTCEPSS rescore
  9. 2026-07-06 02:22 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:30 UTCEPSS rescore
  12. 2026-07-02 17:01 UTCEPSS rescore
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-30 23:21 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:55 UTCEPSS rescore
  20. 2026-06-28 04:55 UTCEPSS rescore
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 05:46 UTCOSV refresh
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 14:04 UTCEPSS rescore
  26. 2026-06-24 14:04 UTCEPSS rescore
  27. 2026-06-23 21:32 UTCEPSS rescore
  28. 2026-06-23 21:32 UTCEPSS rescore
  29. 2026-06-22 14:25 UTCEPSS rescore
  30. 2026-06-22 14:25 UTCEPSS rescore
  31. 2026-06-21 14:56 UTCEPSS rescore
  32. 2026-06-21 14:56 UTCEPSS rescore
  33. 2026-06-21 01:59 UTCEPSS rescore
  34. 2026-06-21 01:59 UTCEPSS rescore
  35. 2026-06-19 19:25 UTCEPSS rescore
  36. 2026-06-19 19:25 UTCEPSS rescore
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-18 17:52 UTCEPSS rescore
  39. 2026-06-17 17:52 UTCEPSS rescore
  40. 2026-06-16 17:52 UTCEPSS rescore
  41. 2026-06-16 17:52 UTCEPSS rescore
  42. 2026-06-15 17:48 UTCEPSS rescore
  43. 2026-06-14 23:17 UTCEPSS rescore
  44. 2026-06-13 23:00 UTCEPSS rescore
  45. 2026-06-13 23:00 UTCEPSS rescore
  46. 2026-06-12 23:11 UTCEPSS rescore
  47. 2026-06-11 13:59 UTCEPSS rescore
  48. 2026-06-10 22:18 UTCEPSS rescore
  49. 2026-06-10 13:22 UTCEPSS rescore
  50. 2026-06-08 16:25 UTCEG score recompute 5.40
  51. 2026-06-08 16:25 UTCGHSA enrichment
  52. 2026-06-08 14:16 UTCEPSS rescore
  53. 2026-06-08 14:16 UTCEPSS rescore
  54. 2026-06-07 15:24 UTCEPSS rescore
  55. 2026-06-07 15:24 UTCEPSS rescore
  56. 2026-06-06 13:47 UTCEPSS rescore
  57. 2026-06-06 13:47 UTCEPSS rescore
  58. 2026-06-05 22:46 UTCEPSS rescore
  59. 2026-06-05 22:46 UTCEPSS rescore
  60. 2026-06-05 06:10 UTCEPSS rescore
  61. 2026-06-05 06:10 UTCEPSS rescore
  62. 2026-06-04 13:12 UTCEPSS rescore
  63. 2026-06-04 13:11 UTCEPSS rescore
  64. 2026-06-03 16:09 UTCOSV refresh
  65. 2026-06-02 20:12 UTCEPSS rescore
  66. 2026-06-01 13:51 UTCEPSS rescore
  67. 2026-06-01 13:51 UTCEPSS rescore
  68. 2026-05-31 22:30 UTCEPSS rescore
  69. 2026-05-31 22:30 UTCEPSS rescore
  70. 2026-05-31 00:16 UTCEPSS rescore
  71. 2026-05-31 00:16 UTCEPSS rescore
  72. 2026-05-29 13:44 UTCEPSS rescore
  73. 2026-05-28 13:44 UTCEPSS rescore
  74. 2026-05-28 13:44 UTCEPSS rescore
  75. 2026-05-28 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-29779?
CVE-2025-29779 is a medium vulnerability published on March 14, 2025. Post-Quantum Secure Feldman's Verifiable Secret Sharing provides a Python implementation of Feldman's Verifiable Secret Sharing (VSS) scheme. In versions 0.8.0b2 and prior, the secureredundantexecution function in feldman_vss.py attempts to mitigate fault injection attacks by executing a function…
When was CVE-2025-29779 disclosed?
CVE-2025-29779 was first published in the National Vulnerability Database on March 14, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-29779 actively exploited?
CVE-2025-29779 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 92.4% of all scored CVEs.
What is the CVSS score of CVE-2025-29779?
CVE-2025-29779 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2025-29779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-29779, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-29779

Explore →

Is Your Infrastructure Affected by CVE-2025-29779?

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