How severe is GHSA-8h58-w33p-wq3g?

No CVSS score has been assigned to GHSA-8h58-w33p-wq3g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8h58-w33p-wq3g?

GHSA-8h58-w33p-wq3g affects the following packages: pgp (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-8h58-w33p-wq3g?

Update pgp to 0.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8h58-w33p-wq3g is resolved across your whole dependency graph.

How do I detect GHSA-8h58-w33p-wq3g in my crates.io dependencies?

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

How do I mitigate GHSA-8h58-w33p-wq3g 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-8h58-w33p-wq3g?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8h58-w33p-wq3g can be triaged on real exposure rather than presence alone.

Is GHSA-8h58-w33p-wq3g actively exploited in the wild?

No public exploit code has been indexed for GHSA-8h58-w33p-wq3g 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-8h58-w33p-wq3g published, and has it been updated?

GHSA-8h58-w33p-wq3g was published on February 13, 2026 and was last updated on February 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.

🦀 crates.io

Not in CISA KEV

GHSA-8h58-w33p-wq3g — pgp

Fix: rpgp/rpgp#625

GHSA-8h58-w33p-wq3g is a remote code execution vulnerability in pgp. A fix is available for pgp — see the affected versions and patch details below.

rPGP affected by crash in message handling for deeply nested messages

Published

Feb 13, 2026

Updated

Feb 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 13, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀pgp

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

Description

Summary

Previous rPGP versions could be caused to crash with a "stack overflow" when parsing messages that contain deeply nested message layers, such as messages with many signatures.

rPGP 0.19.0 resolves this issue with a more robust message handling implementation (via https://github.com/rpgp/rpgp/pull/625).

Impact

An attacker could cause applications to crash in rPGP's message parsing subsystem, when applications attempt to ingest messages.

Attribution

Discovered internally during rPGP development, using a fuzz test suite previously contributed by Christian Reitter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`pgp`	≥ 0.16.0-alpha.0&&< 0.19.0	0.19.0`cargo update -p pgp --precise 0.19.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pgp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pgp to 0.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8h58-w33p-wq3g 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8h58-w33p-wq3g can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8h58-w33p-wq3g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Previous rPGP versions could be caused to crash with a "stack overflow" when parsing messages that contain deeply nested message layers, such as messages with many signatures. rPGP 0.19.0 resolves this issue with a more robust message handling implementation (via https://github.com/rpgp/rpgp/pull/625). ### Impact An attacker could cause applications to crash in rPGP's message parsing subsystem, when applications attempt to ingest messages. ### Attribution Discovered internally during rPGP development, using a fuzz test suite previously contributed by Christian Reitter.

O3 Security · Impact-Aware SCA

Is GHSA-8h58-w33p-wq3g in your dependencies?

O3 Security finds GHSA-8h58-w33p-wq3g across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works