What is GHSA-66FW-43H8-F8P3?

GHSA-66FW-43H8-F8P3 is a low-severity security vulnerability in xmp_toolkit (rust), affecting versions < 1.9.0. It is fixed in 1.9.0.

Which versions of xmp_toolkit are affected by GHSA-66FW-43H8-F8P3?

xmp_toolkit (rust) versions < 1.9.0 is affected.

Is there a fix for GHSA-66FW-43H8-F8P3?

Yes. GHSA-66FW-43H8-F8P3 is fixed in 1.9.0. Upgrade to this version or later.

Is GHSA-66FW-43H8-F8P3 exploitable, and should I be worried?

Whether GHSA-66FW-43H8-F8P3 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.

What actually determines whether GHSA-66FW-43H8-F8P3 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.

GHSA-66FW-43H8-F8P3 in xmp_toolkit

Q: Which versions of xmp_toolkit are affected by GHSA-66FW-43H8-F8P3?

xmp_toolkit (rust) versions < 1.9.0 is affected.

Q: Is there a fix for GHSA-66FW-43H8-F8P3?

Yes. GHSA-66FW-43H8-F8P3 is fixed in 1.9.0. Upgrade to this version or later.

Q: Is GHSA-66FW-43H8-F8P3 exploitable, and should I be worried?

Whether GHSA-66FW-43H8-F8P3 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.

Q: What actually determines whether GHSA-66FW-43H8-F8P3 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.

Q: How do I fix GHSA-66FW-43H8-F8P3?

Upgrade xmp_toolkit to 1.9.0 or later.

Summary

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

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.

Impact

Affected versions

xmp_toolkit (< 1.9.0)

Security releases

xmp_toolkit → 1.9.0 (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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade xmp_toolkit to 1.9.0 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is GHSA-66FW-43H8-F8P3? GHSA-66FW-43H8-F8P3 is a low-severity security vulnerability in xmp_toolkit (rust), affecting versions < 1.9.0. It is fixed in 1.9.0.
Which versions of xmp_toolkit are affected by GHSA-66FW-43H8-F8P3? xmp_toolkit (rust) versions < 1.9.0 is affected.
Is there a fix for GHSA-66FW-43H8-F8P3? Yes. GHSA-66FW-43H8-F8P3 is fixed in 1.9.0. Upgrade to this version or later.
Is GHSA-66FW-43H8-F8P3 exploitable, and should I be worried? Whether GHSA-66FW-43H8-F8P3 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
What actually determines whether GHSA-66FW-43H8-F8P3 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.
How do I fix GHSA-66FW-43H8-F8P3? Upgrade xmp_toolkit to 1.9.0 or later.