CVE-2024-55637

Drupal core contains a potential PHP Object Injection vulnerability that (if combined with another exploit) could lead to Remote Code Execution. It is not directly exploitable.

This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize(). There are no such known exploits in Drupal core.

To help protect against this potential vulnerability, types have been added to properties in some of Drupal core's classes. If an application extends those classes, the same types may need to be specified on the subclass to avoid a TypeError.

This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2024-55637 has a CVSS score of 9.8 (High). The vector is network-reachable, no 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 (10.2.11, 10.3.9, 11.0.8); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-55637? CVE-2024-55637 is a high-severity insecure deserialization vulnerability in drupal/core (composer), affecting versions >= 8.8.0, < 10.2.11. It is fixed in 10.2.11, 10.3.9, 11.0.8. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2024-55637? CVE-2024-55637 has a CVSS score of 9.8 (High). 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.
3. Which packages are affected by CVE-2024-55637?
   • drupal/core (composer) (versions >= 8.8.0, < 10.2.11)
   • drupal/core-recommended (composer) (versions >= 8.8.0, < 10.2.11)
   • drupal/drupal (composer) (versions >= 8.8.0, < 10.2.11)
4. Is there a fix for CVE-2024-55637? Yes. CVE-2024-55637 is fixed in 10.2.11, 10.3.9, 11.0.8. Upgrade to this version or later.
5. Is CVE-2024-55637 exploitable, and should I be worried? Whether CVE-2024-55637 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
6. What actually determines whether CVE-2024-55637 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.
7. How do I fix CVE-2024-55637?
   • Upgrade drupal/core to 10.2.11 or later
   • Upgrade drupal/core to 10.3.9 or later
   • Upgrade drupal/core to 11.0.8 or later
   • Upgrade drupal/core-recommended to 10.2.11 or later
   • Upgrade drupal/core-recommended to 10.3.9 or later
   • Upgrade drupal/core-recommended to 11.0.8 or later
   • Upgrade drupal/drupal to 10.2.11 or later
   • Upgrade drupal/drupal to 10.3.9 or later
   • Upgrade drupal/drupal to 11.0.8 or later