Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍 PyPI
Not in CISA KEV

GHSA-r8gc-qc2c-c7vh — postquantum-feldman-vss

GHSA-r8gc-qc2c-c7vh is a CWE-1240 vulnerability in postquantum-feldman-vss. No vendor fix is recorded yet; mitigation options are listed below.

Post-Quantum Secure Feldman's Verifiable Secret Sharing has Inadequate Fault Injection Countermeasures in `secure_redundant_execution`

Also known asCVE-2025-29779
Published
Mar 14, 2025
Updated
Sep 10, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-r8gc-qc2c-c7vh.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected
🐍postquantum-feldman-vss

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Description:

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:

  1. Python's execution environment cannot guarantee true isolation between redundant executions
  2. The constant-time comparison implementation in Python is subject to timing variations
  3. The randomized execution order and timing provide insufficient protection against sophisticated fault attacks
  4. 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.

Impact:

A successful fault injection attack could allow an attacker to:

  1. Bypass the redundancy check mechanisms
  2. Extract secret polynomial coefficients during share generation or verification
  3. Force the acceptance of invalid shares during verification
  4. Manipulate the commitment verification process to accept fraudulent commitments

This undermines the core security guarantees of the Verifiable Secret Sharing scheme.

References:

Remediation:

Long-term remediation requires reimplementing the security-critical functions in a lower-level language like Rust.

Short-term mitigations:

  1. Deploy the software in environments with physical security controls
  2. Increase the redundancy count (from 5 to a higher number) by modifying the source code
  3. Add external verification of cryptographic operations when possible
  4. Consider using hardware security modules (HSMs) for key operations

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐍PyPIpostquantum-feldman-vssall versionsNo fix

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for postquantum-feldman-vss, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of postquantum-feldman-vss has shipped for GHSA-r8gc-qc2c-c7vh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r8gc-qc2c-c7vh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-r8gc-qc2c-c7vh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**Description:** 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: 1. Python's execution environment cannot guarantee true isolation between redundant executions 2. The constant-time comparison implementation in Python is subject to timing variations 3. The randomized execution order and timing provide insufficient protection against sophisticated fault attacks 4. The error handling may leak timing information about partial execution
O3 Security · Impact-Aware SCA

Is GHSA-r8gc-qc2c-c7vh in your dependencies?

O3 Security finds GHSA-r8gc-qc2c-c7vh across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works
GHSA-r8gc-qc2c-c7vh: postquantum-feldman | O3 Security