What is CVE-2025-49597?

CVE-2025-49597 is a low-severity security vulnerability in handcraftedinthealps/goodby-csv (composer), affecting versions < 1.4.3. It is fixed in 1.4.3.

How severe is CVE-2025-49597?

CVE-2025-49597 has a CVSS score of 3.9 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of handcraftedinthealps/goodby-csv are affected by CVE-2025-49597?

handcraftedinthealps/goodby-csv (composer) versions < 1.4.3 is affected.

Is there a fix for CVE-2025-49597?

Yes. CVE-2025-49597 is fixed in 1.4.3. Upgrade to this version or later.

Is CVE-2025-49597 exploitable, and should I be worried?

Whether CVE-2025-49597 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 CVE-2025-49597 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 CVE-2025-49597?

Upgrade handcraftedinthealps/goodby-csv to 1.4.3 or later.

CVE-2025-49597 in handcraftedinthealps/goodby-csv

Q: How severe is CVE-2025-49597?

CVE-2025-49597 has a CVSS score of 3.9 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of handcraftedinthealps/goodby-csv are affected by CVE-2025-49597?

handcraftedinthealps/goodby-csv (composer) versions < 1.4.3 is affected.

Q: Is there a fix for CVE-2025-49597?

Yes. CVE-2025-49597 is fixed in 1.4.3. Upgrade to this version or later.

Q: Is CVE-2025-49597 exploitable, and should I be worried?

Whether CVE-2025-49597 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 CVE-2025-49597 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 CVE-2025-49597?

Upgrade handcraftedinthealps/goodby-csv to 1.4.3 or later.

Summary

handcraftedinthealps/goodby-csv has Potential Gadget Chain allowing Remote Code Execution

Workarounds

Patch src/Goodby/CSV/Export/Standard/Collection /CallbackCollection.php:

+    public function __wakeup() {
+       throw new \BadMethodCallException('Cannot unserialize ' . __CLASS__);
+    }

However, this is not directly exploitable; a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize(). There are no such known exploits in goodby-csv.

References

Are there any links users can visit to find out more?

Impact

goodby-csv could be used as part of a chain of methods that is exploitable when an insecure deserialization vulnerability exists in an application. This so-called "gadget chain" presents no direct threat but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.

CVE-2025-49597 has a CVSS score of 3.9 (Low). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.3); upgrading removes the vulnerable code path.

Affected versions

handcraftedinthealps/goodby-csv (< 1.4.3)

Security releases

handcraftedinthealps/goodby-csv → 1.4.3 (composer)

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

Has the problem been patched? What versions should users upgrade to?

The problem is patched with Version 1.4.3

Frequently Asked Questions

What is CVE-2025-49597? CVE-2025-49597 is a low-severity security vulnerability in handcraftedinthealps/goodby-csv (composer), affecting versions < 1.4.3. It is fixed in 1.4.3.
How severe is CVE-2025-49597? CVE-2025-49597 has a CVSS score of 3.9 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of handcraftedinthealps/goodby-csv are affected by CVE-2025-49597? handcraftedinthealps/goodby-csv (composer) versions < 1.4.3 is affected.
Is there a fix for CVE-2025-49597? Yes. CVE-2025-49597 is fixed in 1.4.3. Upgrade to this version or later.
Is CVE-2025-49597 exploitable, and should I be worried? Whether CVE-2025-49597 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 CVE-2025-49597 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 CVE-2025-49597? Upgrade handcraftedinthealps/goodby-csv to 1.4.3 or later.