How severe is GHSA-gch5-hwqf-mxhp?

No CVSS score has been assigned to GHSA-gch5-hwqf-mxhp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gch5-hwqf-mxhp?

GHSA-gch5-hwqf-mxhp affects the following packages: intaglio (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-gch5-hwqf-mxhp?

Update intaglio to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gch5-hwqf-mxhp is resolved across your whole dependency graph.

How do I detect GHSA-gch5-hwqf-mxhp in my crates.io dependencies?

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

How do I mitigate GHSA-gch5-hwqf-mxhp 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-gch5-hwqf-mxhp?

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

Is GHSA-gch5-hwqf-mxhp actively exploited in the wild?

No public exploit code has been indexed for GHSA-gch5-hwqf-mxhp 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-gch5-hwqf-mxhp published, and has it been updated?

GHSA-gch5-hwqf-mxhp was published on July 27, 2023 and was last updated on November 8, 2023. 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-gch5-hwqf-mxhp — intaglio

Fix: artichoke/intaglio#236

GHSA-gch5-hwqf-mxhp is a security vulnerability in intaglio. A fix is available for intaglio — see the affected versions and patch details below.

Unsoundness in `intern` methods on `intaglio` symbol interners

Also known asRUSTSEC-2023-0048

Published

Jul 27, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀intaglio

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

Affected versions of this crate have a stacked borrows violation when creating references to interned contents. All interner types are affected.

The flaw was corrected in version 1.9.0 by reordering move and borrowing operations and storing interned contents by raw pointer instead of as a Box.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`intaglio`	all versions	1.9.0`cargo update -p intaglio --precise 1.9.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for intaglio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update intaglio to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gch5-hwqf-mxhp 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-gch5-hwqf-mxhp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-gch5-hwqf-mxhp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of this crate have a stacked borrows violation when creating references to interned contents. All interner types are affected. The flaw was corrected in version 1.9.0 by reordering move and borrowing operations and storing interned contents by raw pointer instead of as a `Box`.

O3 Security · Impact-Aware SCA

Is GHSA-gch5-hwqf-mxhp in your dependencies?

O3 Security finds GHSA-gch5-hwqf-mxhp 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