How severe is GHSA-7r92-3jgr-r65q?

No CVSS score has been assigned to GHSA-7r92-3jgr-r65q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7r92-3jgr-r65q?

GHSA-7r92-3jgr-r65q affects the following packages: pyquorum (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-7r92-3jgr-r65q?

Update pyquorum to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7r92-3jgr-r65q is resolved across your whole dependency graph.

How do I detect GHSA-7r92-3jgr-r65q in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyquorum. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7r92-3jgr-r65q if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-7r92-3jgr-r65q?

O3 pinpoints whether GHSA-7r92-3jgr-r65q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7r92-3jgr-r65q actively exploited in the wild?

No public exploit code has been indexed for GHSA-7r92-3jgr-r65q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-7r92-3jgr-r65q?

GHSA-7r92-3jgr-r65q is classified as CWE-208 (CWE-208). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7r92-3jgr-r65q published, and has it been updated?

GHSA-7r92-3jgr-r65q was published on May 6, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-7r92-3jgr-r65q

Fix: svvqt/pyquorum@1e9ac41

GHSA-7r92-3jgr-r65q is a CWE-208 vulnerability in pyquorum. O3 Security confirms whether GHSA-7r92-3jgr-r65q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

pyquorum: Timing side‑channel in mul_mod

Also known asCVE-2026-44368PYSEC-2026-3028

Published

May 6, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐍pyquorum

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

Impact

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.

Patches

https://github.com/svvqt/pyquorum/releases/tag/v0.2.1

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pyquorum`	all versions	0.2.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyquorum. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update pyquorum to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7r92-3jgr-r65q is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 pinpoints whether GHSA-7r92-3jgr-r65q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7r92-3jgr-r65q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact 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. ### Patches https://github.com/svvqt/pyquorum/releases/tag/v0.2.1

O3 Security · Impact-Aware SCA

Is GHSA-7r92-3jgr-r65q in your dependencies?

O3 detects GHSA-7r92-3jgr-r65q across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works