How severe is GHSA-4fg7-vxc8-qx5w?

No CVSS score has been assigned to GHSA-4fg7-vxc8-qx5w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4fg7-vxc8-qx5w?

GHSA-4fg7-vxc8-qx5w affects the following packages: rage (crates.io), age (crates.io), age (crates.io), age (crates.io), age (crates.io), age (crates.io), age (crates.io), rage (crates.io), and 4 more. Ecosystems affected: crates.io.

How do I fix GHSA-4fg7-vxc8-qx5w?

Update rage to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4fg7-vxc8-qx5w is resolved across your whole dependency graph.

How do I detect GHSA-4fg7-vxc8-qx5w in my crates.io dependencies?

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

How do I mitigate GHSA-4fg7-vxc8-qx5w 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-4fg7-vxc8-qx5w actively exploited in the wild?

No public exploit code has been indexed for GHSA-4fg7-vxc8-qx5w 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-4fg7-vxc8-qx5w published, and has it been updated?

GHSA-4fg7-vxc8-qx5w was published on December 18, 2024 and was last updated on September 10, 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

rage vulnerable to malicious plugin names, recipients, or identities causing arbitrary binary executionGHSA-4fg7-vxc8-qx5w

Fix: str4d/rage@703152e

GHSA-4fg7-vxc8-qx5w is a security vulnerability in rage. A fix is available for rage — see the affected versions and patch details below.

Also known asRUSTSEC-2024-0432RUSTSEC-2024-0433

Published

Dec 18, 2024

Updated

Sep 10, 2026

Affected

12 pkgs

Patched

12 / 12

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

12 pkgs affected

🦀rage🦀age🦀age🦀age🦀age🦀age🦀age🦀rage+4 more

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

A plugin name containing a path separator may allow an attacker to execute an arbitrary binary.

Such a plugin name can be provided to the rage CLI through an attacker-controlled recipient or identity string, or to the following age APIs when the plugin feature flag is enabled:

On UNIX systems, a directory matching age-plugin-* needs to exist in the working directory for the attack to succeed.

The binary is executed with a single flag, either --age-plugin=recipient-v1 or --age-plugin=identity-v1. The standard input includes the recipient or identity string, and the random file key (if encrypting) or the header of the file (if decrypting). The format is constrained by the age-plugin protocol.

An equivalent issue was fixed in the reference Go implementation of age, see advisory GHSA-32gq-x56h-299c.

Thanks to ⬡-49016 for reporting this issue.

Affected Packages

12 total 12 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`rage`	≥ 0.6.0&&< 0.6.1	0.6.1`cargo update -p rage --precise 0.6.1`
🦀crates.io	`age`	≥ 0.6.0&&< 0.6.1	0.6.1`cargo update -p age --precise 0.6.1`
🦀crates.io	`age`	≥ 0.7.0&&< 0.7.2	0.7.2`cargo update -p age --precise 0.7.2`
🦀crates.io	`age`	≥ 0.8.0&&< 0.8.2	0.8.2`cargo update -p age --precise 0.8.2`
🦀crates.io	`age`	≥ 0.9.0&&< 0.9.3	0.9.3`cargo update -p age --precise 0.9.3`
🦀crates.io	`age`	≥ 0.10.0&&< 0.10.1	0.10.1`cargo update -p age --precise 0.10.1`

Detection & mitigation playbook

Open-source dependency

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

A plugin name containing a path separator may allow an attacker to execute an arbitrary binary. Such a plugin name can be provided to the `rage` CLI through an attacker-controlled recipient or identity string, or to the following `age` APIs when the `plugin` feature flag is enabled: - [`age::plugin::Identity::from_str`](https://docs.rs/age/0.11.0/age/plugin/struct.Identity.html#impl-FromStr-for-Identity) (or equivalently [`str::parse::<age::plugin::Identity>()`](https://doc.rust-lang.org/stable/core/primitive.str.html#method.parse)) - [`age::plugin::Identity::default_for_plugin`](https://docs

O3 Security · Impact-Aware SCA

Is GHSA-4fg7-vxc8-qx5w in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works