CVE-2026-1496

Coverity CLI Authentication Bypass

Published Mar 27, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
Vulnerable versions of Coverity Connect lack an error handler in the authentication logic for command line tooling that makes it vulnerable to an authentication bypass. A malicious actor with access to the /token API endpoint that either knows or guesses a valid username, can use this in a specially crafted HTTP request to bypass authentication. Successful exploitation allows the malicious actor to assume all roles and privileges granted to the valid user’s Coverity Connect account.

Analysis

AI-generated

Technical impact

The vulnerability is caused by the absence of an error handler in Coverity Connect's authentication logic for its command‑line tools. A malicious actor who can reach the /token API endpoint and knows or can guess a valid username can send a specially crafted HTTP request that bypasses authentication. Once authenticated, the attacker gains all roles and privileges assigned to the targeted user, allowing full access to the Coverity Connect environment. This is a high‑severity authentication bypass that could lead to unauthorized data exposure and critical changes to the code analysis repository.

Affected Systems

Affected releases are all Coverity Connect versions that are listed as vulnerable: 2024.12.0a, 2024.12.1a, 2024.12.2, 2024.3.0a‑3.2, 2024.6.0a‑6.1a, 2024.9.0a‑9.1a, 2025.0a‑? (specifically 2025.12.0a, 12.1, 3.0a‑3.2, 6.0a‑6.4, 9.0a‑9.3), and 2025.12.1 is a patched release along with 2025.9.3, 6.4, 3.2. Any deployment prior to these patched versions is susceptible.

Risk and Exploitability

With a CVSS score of 9.3 the vulnerability carries a critical risk. Although EPSS is not reported, the attack surface—access to the /token endpoint and knowledge of a username—is generally available to external actors who can communicate with the Coverity server. The exploit requires no privileged local access and can be executed remotely, making it a straightforward privilege escalation attack. The absence of a formal KEV listing does not lessen the potential impact; security teams should treat the vulnerability as an imminent threat.

Remediation

Vendor Solution

Customers are recommended to upgrade to one of the following Coverity patched versions at their earliest availability or deploy documented mitigations. Patched versions: * 2025.12.1 * 2025.12.0A * 2025.9.2A * 2025.9.0A * 2025.6.2A * 2025.6.0A * 2025.3.1A * 2025.3.0A * 2024.12.1A * 2024.12.0A * 2024.9.1A * 2024.9.0A Full Installers: * 2025.12.1 * 2025.9.3 * 2025.6.4 * 2025.3.2 * 2024.12.2


OpenCVE Recommended Actions

  • Upgrade to a patched Coverity Connect release such as 2025.12.1, 2025.9.3, 2025.6.4, or 2025.3.2.
  • If an upgrade cannot be performed immediately, block access to the /token API endpoint using firewall rules or network segmentation.
  • Implement the vendor’s WAF/IDS/IPS mitigation guidance to detect and prevent unauthorized requests to the token endpoint.
  • Verify that the blocking or mitigation rules are in place by attempting unauthenticated access to /token and confirming denial.
  • Continuously monitor audit logs for unusual authentication attempts and enforce least‑privilege user roles as a protective measure.

Generated by OpenCVE AI on March 27, 2026 at 15:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Vulnerable versions of Coverity Connect lack an error handler in the authentication logic for command line tooling that makes it vulnerable to an authentication bypass. A malicious actor with access to the /token API endpoint that either knows or guesses a valid username, can use this in a specially crafted HTTP request to bypass authentication. Successful exploitation allows the malicious actor to assume all roles and privileges granted to the valid user’s Coverity Connect account.
Title Coverity CLI Authentication Bypass
First Time appeared Black Duck
Black Duck coverity
Weaknesses CWE-639
CPEs cpe:2.3:a:black_duck:coverity:*:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.12.0a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.12.1a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.12.2:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.3.0a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.3.1a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.3.2a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.6.0a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.6.1a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.9.0a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2024.9.1a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.12.0a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.12.1:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.3.0a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.3.1a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.3.2:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.6.0a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.6.2a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.6.4:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.9.0a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.9.2a:*:*:*:*:*:*:*
cpe:2.3:a:black_duck:coverity:2025.9.3:*:*:*:*:*:*:*
Vendors & Products Black Duck
Black Duck coverity
References
Metrics cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
BlackDuck
Published
Updated
Mar 27, 2026, 2:36 PM
Reserved
Jan 27, 2026, 3:53 PM
Status
Awaiting Analysis
Published
Mar 27, 2026, 3:16 PM
Modified
Oct 26, 2026, 9:10 PM