Vulnerability in pyquorum (CVE-2026-44368)
Summary
Vulnerability in pyquorum (CVE-2026-44368). Risk of unauthorized operations or information disclosure. Exploitable via mul_mod. Mitigation: upgrade to 0.2.1 or later.
Original description
The description as published by the source.
PyQuorum is a cryptographic library for secret sharing and key management. Prior to 0.2.1, the mul_mod function implements multiplication via a binary expansion loop whose execution time depends on the Hamming weight of the second operand (the exponent). An attacker who can measure the time of secret‑sharing operations (e.g., via a remote service) could progressively recover the values of shares, ultimately leading to secret reconstruction. This vulnerability is fixed in 0.2.1.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44368 has been found in pyquorum.
Attackers can target a specific entry point like mul_mod over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pyquorum to 0.2.1 or later.
If unsure, ask your IT team or search "pyquorum CVE-2026-44368" on the vendor's site.
CVE-2026-44368 (pyquorum) — CWE-208
Attack surface: mul_mod
Patched: 0.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-208) exists in pyquorum. Attackers reach the vulnerable code path via mul_mod.
Check the vendor advisory for the affected versions of pyquorum. Attack surface: mul_mod.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.2.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pyquorum' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pyquorum' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pyquorumを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pyquorum to 0.2.1ステージング環境で 0.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com