dbcve.org
CalciteApplication · Apache

CVE-2026-46718

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-02
Fix available
A fix is available. Upgrade to 1.42.0 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Apache Calcite. This issue affects Apache Calcite: from 1.5.0 before 1.42. Users are recommended to upgrade to version 1.42, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Apache Calcite contains an unsafe reflection vulnerability where externally-controlled input can be used to select and load arbitrary classes or code paths. This unsafe reflection pattern can allow attackers to instantiate unexpected classes or execute code they should not have access to, potentially leading to remote code execution depending on what classes are accessible in the classpath.

MitigationUpgrade Apache Calcite to version 1.42 or later. If immediate upgrading is not possible, validate and sanitize all user-supplied input that is used in reflection-based operations, and restrict the set of allowable classes that can be loaded.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CalciteApplication
Affected:>= 1.5.0, < 1.42.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Apache Calcite library files
    Search for calcite JAR files in your application dependencies: 'find . -name "*calcite*.jar"' or check your build manifest/Maven POM for calcite dependencies
    Affected if Apache Calcite library is present in the environment
  2. Determine installed Calcite version
    Check the calcite JAR file name or inspect its manifest: 'jar tf calcite-*.jar | grep META-INF/MANIFEST.MF' then read the Implementation-Version attribute, or run 'grep -r calcite.version' in build files
    Affected if Version is 1.5.0 through 1.41.0 inclusive
  3. Identify if Calcite is exposed to untrusted input
    Review application code and configuration for user-supplied input that reaches Calcite's SQL parsing, schema definition, or UDF loading mechanisms. Check for endpoints or APIs that pass external values to Calcite processors
    Affected if Untrusted or user-controlled input can reach Calcite's reflection-based class loading or code execution paths
  4. Audit Calcite adapter and function configurations
    Inspect Calcite adapter configs (e.g., JSON, CSV, JDBC adapter definitions) and custom function registrations for dynamic class references that could be influenced by external input
    Affected if Dynamic class loading or function references are configurable via external parameters

You are affected if Apache Calcite version 1.5.0 through 1.41 is in use AND untrusted input can reach Calcite's reflection or dynamic class loading mechanisms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.42.0 or later
Fixed in 1.42.0
Interim mitigation

Upgrade Apache Calcite to version 1.42 or later. If immediate upgrading is not possible, validate and sanitize all user-supplied input that is used in reflection-based operations, and restrict the set of allowable classes that can be loaded.

Recommended fix High confidence

1.42.0

  1. Identify all project dependencies that include Apache Calcite (check pom.xml, build.gradle, or similar dependency management files)
  2. Locate the Calcite dependency declaration and update the version from the current version to 1.42.0
  3. For Maven projects: Update <version>org.apache.calcite</version> to 1.42.0 or update the property defining Calcite version
  4. For Gradle projects: Update the Calcite dependency to 'org.apache.calcite:calcite-core:1.42.0'
  5. Rebuild the project to ensure the new version is correctly resolved
  6. Run existing test suites to verify the upgrade does not break functionality
  7. Verify that the application starts and operates normally with the updated library
Caveat Check Apache Calcite 1.42 release notes for any breaking changes between your current version and 1.42

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Calcite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46718 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data