GHSA-4FG7-VXC8-QX5W

GHSA-4FG7-VXC8-QX5W is a medium-severity security vulnerability in rage (rust), affecting versions = 0.6.0. It is fixed in 0.6.1, 0.7.2, 0.8.2, 0.9.3, 0.10.1, 0.11.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

rage vulnerable to malicious plugin names, recipients, or identities causing arbitrary binary execution

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.

Impact

Affected versions

rage (= 0.6.0) age (= 0.6.0) age (>= 0.7.0, < 0.7.2) age (>= 0.8.0, < 0.8.2) age (>= 0.9.0, < 0.9.3) age (= 0.10.0) age (= 0.11.0) rage (>= 0.7.0, < 0.7.2) rage (>= 0.8.0, < 0.8.2) rage (>= 0.9.0, < 0.9.3) rage (= 0.10.0) rage (= 0.11.0)

Security releases

rage → 0.6.1 (rust) age → 0.6.1 (rust) age → 0.7.2 (rust) age → 0.8.2 (rust) age → 0.9.3 (rust) age → 0.10.1 (rust) age → 0.11.1 (rust) rage → 0.7.2 (rust) rage → 0.8.2 (rust) rage → 0.9.3 (rust) rage → 0.10.1 (rust) rage → 0.11.1 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

rage to 0.6.1 or later; age to 0.6.1 or later; age to 0.7.2 or later; age to 0.8.2 or later; age to 0.9.3 or later; age to 0.10.1 or later; age to 0.11.1 or later; rage to 0.7.2 or later; rage to 0.8.2 or later; rage to 0.9.3 or later; rage to 0.10.1 or later; rage to 0.11.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-4FG7-VXC8-QX5W? GHSA-4FG7-VXC8-QX5W is a medium-severity security vulnerability in rage (rust), affecting versions = 0.6.0. It is fixed in 0.6.1, 0.7.2, 0.8.2, 0.9.3, 0.10.1, 0.11.1.
  2. Which packages are affected by GHSA-4FG7-VXC8-QX5W?
    • rage (rust) (versions = 0.6.0)
    • age (rust) (versions = 0.6.0)
  3. Is there a fix for GHSA-4FG7-VXC8-QX5W? Yes. GHSA-4FG7-VXC8-QX5W is fixed in 0.6.1, 0.7.2, 0.8.2, 0.9.3, 0.10.1, 0.11.1. Upgrade to this version or later.
  4. Is GHSA-4FG7-VXC8-QX5W exploitable, and should I be worried? Whether GHSA-4FG7-VXC8-QX5W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-4FG7-VXC8-QX5W is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-4FG7-VXC8-QX5W?
    • Upgrade rage to 0.6.1 or later
    • Upgrade age to 0.6.1 or later
    • Upgrade age to 0.7.2 or later
    • Upgrade age to 0.8.2 or later
    • Upgrade age to 0.9.3 or later
    • Upgrade age to 0.10.1 or later
    • Upgrade age to 0.11.1 or later
    • Upgrade rage to 0.7.2 or later
    • Upgrade rage to 0.8.2 or later
    • Upgrade rage to 0.9.3 or later
    • Upgrade rage to 0.10.1 or later
    • Upgrade rage to 0.11.1 or later

Stop the waste.
Protect your environment with Kodem.