CVE-2020-13955

CVE-2020-13955 is a medium-severity security vulnerability in org.apache.calcite:calcite-core (maven), affecting versions < 1.26.0. It is fixed in 1.26.0.

Check whether CVE-2020-13955 affects your applications

Kodem tells you whether this CVE is present, reachable, and actually executing in your application, so you know if it matters.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence. Only the CVEs that actually run in production.

Summary

Missing Authentication for Critical Function in Apache Calcite

"HttpUtils#getURLConnection method disables explicitly hostname verification for HTTPS connections making clients vulnerable to man-in-the-middle attacks. Calcite uses this method internally to connect with Druid and Splunk so information leakage may happen when using the respective Calcite adapters. The method itself is in a utility class so people may use it to create vulnerable HTTPS connections for other applications. From Apache Calcite 1.26 onwards, the hostname verification will be performed using the default JVM truststore."

Impact

CVE-2020-13955 has a CVSS score of 5.9 (Medium). 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 (1.26.0); upgrading removes the vulnerable code path.

Affected versions

org.apache.calcite:calcite-core (< 1.26.0) org.apache.calcite:calcite-druid (< 1.26.0) org.apache.calcite:calcite-splunk (< 1.26.0)

Security releases

org.apache.calcite:calcite-core → 1.26.0 (maven) org.apache.calcite:calcite-druid → 1.26.0 (maven) org.apache.calcite:calcite-splunk → 1.26.0 (maven)

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 environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.calcite:calcite-core to 1.26.0 or later; org.apache.calcite:calcite-druid to 1.26.0 or later; org.apache.calcite:calcite-splunk to 1.26.0 or later

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

Frequently Asked Questions

  1. What is CVE-2020-13955? CVE-2020-13955 is a medium-severity security vulnerability in org.apache.calcite:calcite-core (maven), affecting versions < 1.26.0. It is fixed in 1.26.0.
  2. How severe is CVE-2020-13955? CVE-2020-13955 has a CVSS score of 5.9 (Medium). 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-2020-13955?
    • org.apache.calcite:calcite-core (maven) (versions < 1.26.0)
    • org.apache.calcite:calcite-druid (maven) (versions < 1.26.0)
    • org.apache.calcite:calcite-splunk (maven) (versions < 1.26.0)
  4. Is there a fix for CVE-2020-13955? Yes. CVE-2020-13955 is fixed in 1.26.0. Upgrade to this version or later.
  5. Is CVE-2020-13955 exploitable, and should I be worried? Whether CVE-2020-13955 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-2020-13955 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-2020-13955?
    • Upgrade org.apache.calcite:calcite-core to 1.26.0 or later
    • Upgrade org.apache.calcite:calcite-druid to 1.26.0 or later
    • Upgrade org.apache.calcite:calcite-splunk to 1.26.0 or later

Other vulnerabilities in org.apache.calcite:calcite-core

Stop the waste.
Protect your environment with Kodem.