CVE-2026-64640 Vulnerability Analysis & Exploit Details

CVE-2026-64640
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2026-64640 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-64640 Details

Status: Modified

Published on: 06 Aug 2026, 09:16 UTC

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-64640 Vulnerability Summary

CVE-2026-64640: Apache Polaris did not consistently validate storage locations supplied during table and view registration. An authenticated principal with permission to register a table or view could, depending on the affected release and registration path, cause Polaris to use the catalog's storage credentials to read a caller-selected Iceberg metadata file before verifying that the file was within the catalog's allowed storage locations. If the catalog's underlying credentials could read an object outside that boundary, this could disclose limited information from the object. Polaris could also accept registration metadata located within an allowed location that contained references to storage locations outside the allowed boundary. This second condition did not itself cause Polaris to read the referenced external locations during registration. The demonstrated impact is limited to confidentiality. No unauthorized data modification or availability impact has been demonstrated. The server-side read requires a deployment using S3 credential vending and an object outside the allowed locations that the catalog's underlying storage credentials can read. Exploitation requires an authenticated principal with table- or view-registration privileges.

Assessing the Risk of CVE-2026-64640

Access Complexity Graph

The exploitability of CVE-2026-64640 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-64640

CVE-2026-64640 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-64640, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-64640, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-64640 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-64640 poses no threat to data integrity.
  • Availability: None
    CVE-2026-64640 does not impact system availability.

CVE-2026-64640 References

External References

CWE Common Weakness Enumeration

CWE-863

Vulnerable Configurations

  • cpe:2.3:a:apache:polaris:0.9.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:0.9.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:0.9.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:0.9.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:0.9.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:0.9.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:0.9.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:0.9.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:0.9.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:0.9.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:0.9.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:0.9.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:0.9.0:rc6:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:0.9.0:rc6:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:0.10.0:beta:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:0.10.0:beta:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.0:rc5:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.0:rc6:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.0:rc6:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.1:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.1:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.0.1:rc0:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.0.1:rc0:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.1.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.1.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.2.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.2.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.3.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.3.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.3.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.3.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.3.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.3.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.4.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.4.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.4.1:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.4.1:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.4.1:rc0:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.4.1:rc0:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.5.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.5.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:apache:polaris:1.6.0:-:*:*:*:*:*:*
    cpe:2.3:a:apache:polaris:1.6.0:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-64640: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-89172 – Improper protection of physical side channels vulnerability in Microchip AN1044, Microchip AN953, and Microchip SW300052. This issue affects AN104...
  • CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...
  • CVE-2026-85198 – The MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO plugin for WordPress is vulnerable to generic SQL Injection via URL Path i...
  • CVE-2026-78175 – The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and includin...
  • CVE-2026-78159 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.3 via the parse_arra...