How severe is GHSA-h29g-c9cx-c73q?

No CVSS score has been assigned to GHSA-h29g-c9cx-c73q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h29g-c9cx-c73q?

GHSA-h29g-c9cx-c73q affects the following packages: torrentpier/torrentpier (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-h29g-c9cx-c73q?

Update torrentpier/torrentpier to 2.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h29g-c9cx-c73q is resolved across your whole dependency graph.

How do I detect GHSA-h29g-c9cx-c73q in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for torrentpier/torrentpier, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h29g-c9cx-c73q 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.

Is GHSA-h29g-c9cx-c73q actively exploited in the wild?

No public exploit code has been indexed for GHSA-h29g-c9cx-c73q 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.

When was GHSA-h29g-c9cx-c73q published, and has it been updated?

GHSA-h29g-c9cx-c73q was published on May 11, 2026 and was last updated on May 11, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

torrentpier has PHP Serialize InjectionsGHSA-h29g-c9cx-c73q

GHSA-h29g-c9cx-c73q is a remote code execution vulnerability in torrentpier/torrentpier. A fix is available for torrentpier/torrentpier — see the affected versions and patch details below.

Published

May 11, 2026

Updated

May 11, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 11, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘torrentpier/torrentpier

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

Description

Summary

Hi, there. We've found PHP Serialize Injections in your project “torrentpier". According to the OWASP, it can pose a significant risk: enable an attacker to modify serialized objects in order to inject malicious data into the application code, resulting in code execution or an arbitrary reading of the file on any vulnerable system.

Details

In the attachment you can find a report with the number of vulnerabilities, their types and the vulnerable files. To view the lines of vulnerable code you may scan your project with the "PHP Secure" vulnerability scanner with a full access to it.

PoC

About Us

We are a team of developers of the PHP Secure vulnerability scanner. First, we checked your code automatically. Then we reviewed the vulnerable code more deeply manually and felt it was necessary to report about it to you. We suggest you scanning your code and address vulnerabilities as soon as possible to prevent a potential breach.

If you have any questions, email us at [email protected]"

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`torrentpier/torrentpier`	all versions	2.4.4`composer require torrentpier/torrentpier:^2.4.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for torrentpier/torrentpier, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update torrentpier/torrentpier to 2.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h29g-c9cx-c73q 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.

Frequently Asked Questions

### Summary Hi, there. We've found PHP Serialize Injections in your project “torrentpier". According to the OWASP, it can pose a significant risk: enable an attacker to modify serialized objects in order to inject malicious data into the application code, resulting in code execution or an arbitrary reading of the file on any vulnerable system. ### Details In the attachment you can find a report with the number of vulnerabilities, their types and the vulnerable files. To view the lines of vulnerable code you may scan your project with the "[PHP Secure](

O3 Security · Impact-Aware SCA

Is GHSA-h29g-c9cx-c73q in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works