What is CVE-2025-15504?

CVE-2025-15504 is a low-severity null pointer dereference vulnerability in lief (pip), affecting versions < 0.17.2. It is fixed in 0.17.2. The application dereferences a null pointer, causing a crash.

How severe is CVE-2025-15504?

CVE-2025-15504 has a CVSS score of 3.3 (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 lief are affected by CVE-2025-15504?

lief (pip) versions < 0.17.2 is affected.

Is there a fix for CVE-2025-15504?

Yes. CVE-2025-15504 is fixed in 0.17.2. Upgrade to this version or later.

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

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

Upgrade: lief to 0.17.2 or later, lief to 0.17.2 or later.

CVE-2025-15504 in lief

Q: How severe is CVE-2025-15504?

CVE-2025-15504 has a CVSS score of 3.3 (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 lief are affected by CVE-2025-15504?

lief (pip) versions < 0.17.2 is affected.

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

Yes. CVE-2025-15504 is fixed in 0.17.2. Upgrade to this version or later.

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

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

Upgrade: lief to 0.17.2 or later, lief to 0.17.2 or later.

Summary

LIEF is vulnerable to segmentation fault

A security flaw has been discovered in lief-project LIEF up to 0.17.1. Affected by this issue is the function Parser::parse_binary of the file src/ELF/Parser.tcc of the component ELF Binary Parser. The manipulation results in null pointer dereference. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. Upgrading to version 0.17.2 can resolve this issue. The patch is identified as 81bd5d7ea0c390563f1c4c017c9019d154802978. It is recommended to upgrade the affected component.

Impact

The application dereferences a null pointer, causing a crash. Typical impact: denial of service via crash.

CVE-2025-15504 has a CVSS score of 3.3 (Low). The vector is requires local access, low 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 (0.17.2); upgrading removes the vulnerable code path.

Affected versions

lief (< 0.17.2) lief (< 0.17.2)

Security releases

lief → 0.17.2 (pip) lief → 0.17.2 (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 the following packages to resolve this vulnerability:

lief to 0.17.2 or later; lief to 0.17.2 or later

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

Frequently Asked Questions

What is CVE-2025-15504? CVE-2025-15504 is a low-severity null pointer dereference vulnerability in lief (pip), affecting versions < 0.17.2. It is fixed in 0.17.2. The application dereferences a null pointer, causing a crash.
How severe is CVE-2025-15504? CVE-2025-15504 has a CVSS score of 3.3 (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 lief are affected by CVE-2025-15504? lief (pip) versions < 0.17.2 is affected.
Is there a fix for CVE-2025-15504? Yes. CVE-2025-15504 is fixed in 0.17.2. Upgrade to this version or later.
Is CVE-2025-15504 exploitable, and should I be worried? Whether CVE-2025-15504 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-15504 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-15504?
- Upgrade lief to 0.17.2 or later
- Upgrade lief to 0.17.2 or later

Other vulnerabilities in lief

CVE-IDSeverityPackage summary

CVE-2024-31636Lowlief: LIEF obtain sensitive information via the name parameter CVE-2022-43171Highlief: LIEF heap buffer overflow in the LIEF::MachO::BinaryParser::parse_dyldinfo_generic_bind CVE-2022-40922Highlief: LIEF vulnerable to denial of service through segmentation fault CVE-2022-40923Mediumlief: LIEF vulnerable to denial of service through segmentation fault CVE-2022-38306Mediumlief: LIEF vulnerable to heap based buffer overflow