What is the CVSS score of CVE-2025-61673?

CVE-2025-61673 has a CVSS 3.1 base score of 8.6 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L. EPSS exploitation probability: 0.4%.

Which versions of Karapace are affected by CVE-2025-61673?

Karapace versions 5.0.0 and 5.0.1 contain a critical authentication bypass in OAuth 2.0 configuration that allows unauthenticated access to Schema Registry endpoints, exposing schema data and…. A patch is available.

How to fix or mitigate CVE-2025-61673?

Within 24 hours: Inventory all Karapace deployments and identify instances running versions 5.0.0 or 5.0.1 with OAuth 2.0 enabled. Within 7 days: Upgrade all affected instances to Karapace version 5.0.2 or later. Within 30 days: Conduct audit of Schema Registry access logs for unauthorized requests lacking Authorization headers and review all schema modifications during the vulnerability window.

Karapace CVE-2025-61673

EUVD-2025-33196 HIGH

Authentication Bypass Using an Alternate Path or Channel (CWE-288)

2025-10-03 security-advisories@github.com

Authentication Bypass

8.6

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.6 HIGH

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

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

High

Availability

Low

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:25 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

5.0.2

EUVD ID Assigned

Mar 13, 2026 - 19:29 euvd

EUVD-2025-33196

Analysis Generated

Mar 13, 2026 - 19:29 vuln.today

CVE Published

Oct 03, 2025 - 22:15 nvd

HIGH 8.6

DescriptionGitHub Advisory

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.

Analysis

Technical ContextAI

An authentication bypass vulnerability allows attackers to circumvent login mechanisms and gain unauthorized access without valid credentials.

RemediationAI

Implement robust authentication mechanisms. Use multi-factor authentication. Review authentication logic for bypass conditions. Remove default credentials.