CVE-2026-64640 Apache CVE debrief

Who should care

Users of Apache Polaris, especially those with authenticated principals having table- or view-registration privileges, should review and mitigate this vulnerability to prevent potential unauthorized information disclosure.

Technical summary

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.

Defensive priority

Authenticated users with table- or view-registration privileges could potentially exploit this vulnerability to disclose limited information.

Recommended defensive actions

• Review and restrict table and view registration permissions to minimize the attack surface
• Verify and enforce strict validation of storage locations for Iceberg metadata files
• Monitor for and limit S3 credential vending to necessary services and users
• Implement compensating controls to detect and respond to potential unauthorized reads
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

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.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.