How severe is GHSA-9cc5-2pq7-hfj8?

No CVSS score has been assigned to GHSA-9cc5-2pq7-hfj8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9cc5-2pq7-hfj8?

GHSA-9cc5-2pq7-hfj8 affects the following packages: xmas-elf (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-9cc5-2pq7-hfj8?

Update xmas-elf to 0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9cc5-2pq7-hfj8 is resolved across your whole dependency graph.

How do I detect GHSA-9cc5-2pq7-hfj8 in my crates.io dependencies?

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

How do I mitigate GHSA-9cc5-2pq7-hfj8 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-9cc5-2pq7-hfj8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9cc5-2pq7-hfj8 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-9cc5-2pq7-hfj8 published, and has it been updated?

GHSA-9cc5-2pq7-hfj8 was published on March 26, 2025 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

GHSA-9cc5-2pq7-hfj8 — xmas-elf

Fix: nrc/xmas-elf@57685c3

GHSA-9cc5-2pq7-hfj8 is a security vulnerability in xmas-elf. A fix is available for xmas-elf — see the affected versions and patch details below.

xmas-elf potential out-of-bounds read with a malformed ELF file and the HashTable API.

Also known asRUSTSEC-2025-0018

Published

Mar 26, 2025

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

🦀xmas-elf

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 only validated the index argument of HashTable::get_bucket and HashTable::get_chain against the input-controlled bucket_count and chain_count fields, but not against the size of the ELF section. As a result, a malformed ELF file could trigger out-of-bounds reads in a consumer of the HashTable API by setting these fields to inappropriately large values that would fall outside the relevant hash table section, and by introducing correspondingly out-of-bounds hash table indexes elsewhere in the ELF file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`xmas-elf`	all versions	0.10`cargo update -p xmas-elf --precise 0.10`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xmas-elf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update xmas-elf to 0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9cc5-2pq7-hfj8 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Affected versions of this crate only validated the `index` argument of `HashTable::get_bucket` and `HashTable::get_chain` against the input-controlled `bucket_count` and `chain_count` fields, but not against the size of the ELF section. As a result, a malformed ELF file could trigger out-of-bounds reads in a consumer of the HashTable API by setting these fields to inappropriately large values that would fall outside the relevant hash table section, and by introducing correspondingly out-of-bounds hash table indexes elsewhere in the ELF file.

O3 Security · Impact-Aware SCA

Is GHSA-9cc5-2pq7-hfj8 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works