How severe is GHSA-66fw-43h8-f8p3?

No CVSS score has been assigned to GHSA-66fw-43h8-f8p3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-66fw-43h8-f8p3?

GHSA-66fw-43h8-f8p3 affects the following packages: xmp_toolkit (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-66fw-43h8-f8p3?

Update xmp_toolkit to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-66fw-43h8-f8p3 is resolved across your whole dependency graph.

How do I detect GHSA-66fw-43h8-f8p3 in my crates.io dependencies?

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

How do I mitigate GHSA-66fw-43h8-f8p3 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-66fw-43h8-f8p3?

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

Is GHSA-66fw-43h8-f8p3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-66fw-43h8-f8p3 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-66fw-43h8-f8p3 published, and has it been updated?

GHSA-66fw-43h8-f8p3 was published on July 26, 2024 and was last updated on October 28, 2025. 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-66fw-43h8-f8p3 — xmp_toolkit

Fix: adobe/xmp-toolkit-rs#232

GHSA-66fw-43h8-f8p3 is a security vulnerability in xmp_toolkit. A fix is available for xmp_toolkit — see the affected versions and patch details below.

XMP Toolkit's `XmpFile::close` can trigger undefined behavior

Also known asRUSTSEC-2024-0360

Published

Jul 26, 2024

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀xmp_toolkit

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 the crate failed to catch C++ exceptions raised within the XmpFile::close function. If such an exception occurred, it would trigger undefined behavior, typically a process abort.

This is best demonstrated in issue #230, where a race condition causes the close call to fail due to file I/O errors.

This was fixed in PR #232 (released as crate version 1.9.0), which now safely handles the exception.

For backward compatibility, the existing API ignores the error. A new API XmpFile::try_close was added to allow callers to receive and process the error result.

Users of all prior versions of xmp_toolkit are encouraged to update to version 1.9.0 to avoid undefined behavior.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`xmp_toolkit`	all versions	1.9.0`cargo update -p xmp_toolkit --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 xmp_toolkit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update xmp_toolkit to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-66fw-43h8-f8p3 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-66fw-43h8-f8p3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-66fw-43h8-f8p3. 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 the crate failed to catch C++ exceptions raised within the `XmpFile::close` function. If such an exception occurred, it would trigger undefined behavior, typically a process abort. This is best demonstrated in [issue #230](https://github.com/adobe/xmp-toolkit-rs/issues/230), where a race condition causes the `close` call to fail due to file I/O errors. This was fixed in [PR #232](https://github.com/adobe/xmp-toolkit-rs/pull/232) (released as crate version 1.9.0), which now safely handles the exception. For backward compatibility, the existing API ignores the error. A ne

O3 Security · Impact-Aware SCA

Is GHSA-66fw-43h8-f8p3 in your dependencies?

O3 Security finds GHSA-66fw-43h8-f8p3 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