How severe is GHSA-32gq-x56h-299c?

No CVSS score has been assigned to GHSA-32gq-x56h-299c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-32gq-x56h-299c?

GHSA-32gq-x56h-299c affects the following packages: filippo.io/age (Go). Ecosystems affected: Go.

How do I fix GHSA-32gq-x56h-299c?

Update filippo.io/age to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-32gq-x56h-299c is resolved across your whole dependency graph.

How do I detect GHSA-32gq-x56h-299c in my Go dependencies?

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

How do I mitigate GHSA-32gq-x56h-299c 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-32gq-x56h-299c actively exploited in the wild?

No public exploit code has been indexed for GHSA-32gq-x56h-299c 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-32gq-x56h-299c published, and has it been updated?

GHSA-32gq-x56h-299c 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.

🐹 Go

Not in CISA KEV

age vulnerable to malicious plugin names, recipients, or identities causing arbitrary binary executionGHSA-32gq-x56h-299c

Fix: FiloSottile/age@482cf6f

GHSA-32gq-x56h-299c is a security vulnerability in filippo.io/age. A fix is available for filippo.io/age — see the affected versions and patch details below.

Also known asGO-2024-3344

Published

Dec 18, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐹filippo.io/age

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go 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 age CLI through an attacker-controlled recipient or identity string, or to the plugin.NewIdentity, plugin.NewIdentityWithoutData, or plugin.NewRecipient APIs.

On UNIX systems, a directory matching ${TMPDIR:-/tmp}/age-plugin-* needs to exist 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 by the rage project, see advisory GHSA-4fg7-vxc8-qx5w.

Thanks to ⬡-49016 for reporting this.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`filippo.io/age`	all versions	1.2.1`go get filippo.io/age@v1.2.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for filippo.io/age, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update filippo.io/age to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-32gq-x56h-299c 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 age CLI through an attacker-controlled recipient or identity string, or to the [`plugin.NewIdentity`](https://pkg.go.dev/filippo.io/age/plugin#NewIdentity), [`plugin.NewIdentityWithoutData`](https://pkg.go.dev/filippo.io/age/plugin#NewIdentityWithoutData), or [`plugin.NewRecipient`](https://pkg.go.dev/filippo.io/age/plugin#NewRecipient) APIs. On UNIX systems, a directory matching `${TMPDIR:-/tmp}/age-plugin-*` needs to exist for the attack to succeed. The

O3 Security · Impact-Aware SCA

Is GHSA-32gq-x56h-299c in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works