NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
MEDIUM severity

Publify vulnerable to code injectionGHSA-w78q-4w34-jrjx

MEDIUMFix: publify/publify@b50df05

GHSA-w78q-4w34-jrjx is a medium-severity (CVSS 6.5) Code Injection vulnerability in publify_core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for publify_core — see the affected versions and patch details below.

Also known asBIT-publify-2022-0578CVE-2022-0578
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.47%0.94%1.41%0.2%0.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
💎publify_core

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

Description

Code Injection in GitHub repository publify/publify prior to 9.2.8.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemspublify_coreall versions9.2.8bundle update publify_core --conservative

Affected Products

1 product · 1 configurations
Application
publifypublify_project
< 9.2.8
range
Exploits & PoCs
1

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

Code Injection in GitHub repository publify/publify prior to 9.2.8.

huntr.devNVDMay 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 publify_core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update publify_core to 9.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w78q-4w34-jrjx is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

Code Injection in GitHub repository publify/publify prior to 9.2.8.
O3 Security · Impact-Aware SCA

Is GHSA-w78q-4w34-jrjx in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works
Publify vulnerable to code injection (Medium 6.5)