An authentication bypass vulnerability in Karapace versions 5.0.0 and 5.0.1 allows unauthenticated attackers to read and write to protected Schema Registry endpoints, posing a severe risk to data integrity.

This flaw involves a failure to validate the Authorization header when using OAuth 2.0 Bearer Token authentication, effectively skipping the security check for unauthenticated requests. An attacker can interact with the Schema Registry without providing valid credentials, bypassing intended access controls.

The ability for an unauthenticated user to read or modify the Schema Registry can lead to unauthorized data disclosure or corruption of data schemas. Given the CVSS score of 8.6, this vulnerability is classified as High severity because it allows complete circumvention of security controls, potentially impacting the entire data pipeline and downstream applications.

Immediate Action: Update the Karapace installation to version 5.0.2 or later to address the authentication validation logic failure.

Proactive Monitoring: Review access logs for requests to Schema Registry endpoints that lack an Authorization header or exhibit anomalous patterns from unauthorized sources.

Compensating Controls: Implement network-level access controls or a Web Application Firewall to restrict traffic to the Schema Registry to known, trusted IP addresses until the patch is applied.

Public Exploit Available: No — there is no confirmed public exploit available.

The vulnerability represents a significant security oversight in the OAuth authentication implementation of Karapace. Organizations utilizing OAuth 2.0 with the affected versions must prioritize upgrading to version 5.0.2 to restore proper authentication enforcement and prevent unauthorized access to sensitive registry data.