CVE-2025-61673
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-03

Last updated on: 2025-10-06

Assigner: GitHub, Inc.

Description
Karapace is an open-source implementation of Kafka REST and Schema Registry. Versions 5.0.0 and 5.0.1 contain an authentication bypass vulnerability when configured to use OAuth 2.0 Bearer Token authentication. If a request is sent without an Authorization header, the token validation logic is skipped entirely, allowing an unauthenticated user to read and write to Schema Registry endpoints that should otherwise be protected. This effectively renders the OAuth authentication mechanism ineffective. This issue is fixed in version 5.0.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-03
Last Modified
2025-10-06
Generated
2026-06-16
AI Q&A
2025-10-04
EPSS Evaluated
2026-06-14
NVD
CVE-2025-61673
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
aiven-open karapace 5.0.2
aiven-open karapace 5.0.0
aiven-open karapace 5.0.1
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-288 The product requires authentication, but the product has an alternate path or channel that does not require authentication.
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is an authentication bypass in Karapace versions 5.0.0 and 5.0.1 when using OAuth 2.0 Bearer Token authentication. If a request is made without an Authorization header, the system skips token validation, allowing unauthenticated users to access and modify Schema Registry endpoints that should be protected. This means the OAuth authentication mechanism does not work as intended.

Impact Analysis

The vulnerability allows unauthenticated users to read and write to protected Schema Registry endpoints. This can lead to unauthorized access to sensitive data and unauthorized modifications, potentially compromising data integrity and confidentiality.

Mitigation Strategies

Upgrade Karapace to version 5.0.2 or later, as this version contains the fix for the authentication bypass vulnerability. Until the upgrade can be performed, consider disabling OAuth 2.0 Bearer Token authentication or restricting access to the Schema Registry endpoints to trusted networks or users to prevent unauthorized access.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-61673. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart