Skip to content

← Actionable
Medium, CVSS 5.4amended

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

CVE-2025-29779GHSA-r8gc-qc2c-c7vh

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI postquantum-feldman-vss

    Affected
    <= 0.8.0b2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.4 · CVSS:4.0/AV:P/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2025-29779: 0.18% estimated exploitation activity in the next 30 days; percentile 8.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Description: The secureredundantexecution function in feldmanvss.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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-r8gc-qc2c-c7vh

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-r8gc-qc2c-c7vh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-29779

Advisory: Post-Quantum Secure Feldman's Verifiable Secret Sharing has Inadequate Fault Injection Countermeasures in `secure_redundant_execution`
IDs: CVE-2025-29779, GHSA-r8gc-qc2c-c7vh
Record: https://patchnext.com/advisories/cve-2025-29779 (revision 3, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI postquantum-feldman-vss: affected <= 0.8.0b2

## Suggested inspection (read-only)
- `python -m pip show postquantum-feldman-vss`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on postquantum-feldman-vss.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-r8gc-qc2c-c7vh (OSV record GHSA-r8gc-qc2c-c7vh lists affected ranges: PyPI postquantum-feldman-vss >=0 <=0.8.0b2)
- Verified: https://github.com/advisories/GHSA-r8gc-qc2c-c7vh (GitHub-reviewed advisory GHSA-r8gc-qc2c-c7vh lists affected ranges: PyPI postquantum-feldman-vss >=0 <=0.8.0b2)

Commands are suggestions: review each one before running it.

Loading voting…