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

GHSA-9w7f-m4j4-j3xw

CRITICALFix: Gerapy/Gerapy@49bcb19

GHSA-9w7f-m4j4-j3xw is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in gerapy. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-9w7f-m4j4-j3xw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Gerapy may cause remote code execution

Also known asCVE-2021-43857PYSEC-2021-867
Published
Jan 6, 2022
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐍gerapy

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

project_configure function exist remote code execute in Gerapy < 0.9.8

Patches

Patched in version 0.9.8, please install with:

pip3 install -U gerapy

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIgerapyall versions0.9.8
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-50640remotepython

Gerapy 0.9.7 - Remote Code Execution (RCE) (Authenticated)

by Jeremiasz Pluta · Jan 5, 2022

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gerapy. 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.

  2. Fix

    Update gerapy to 0.9.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9w7f-m4j4-j3xw is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-9w7f-m4j4-j3xw 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-9w7f-m4j4-j3xw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact project_configure function exist remote code execute in Gerapy < 0.9.8 ### Patches Patched in version 0.9.8, please install with: ``` pip3 install -U gerapy ```
O3 Security · Impact-Aware SCA

Is GHSA-9w7f-m4j4-j3xw in your dependencies?

O3 detects GHSA-9w7f-m4j4-j3xw across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-9w7f-m4j4-j3xw: Gerapy may cause… | O3 Security