CVE-2026-1496: Coverity CLI Authentication Bypass

Published Mar 27, 2026
·
Updated

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.

Affected Software

1 affected component
Synopsys Coverity Connect

Remediation

Information

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

Event History

Mar 27, 2026
CVE Published
via MITRE·02:14 PM
Data Sourced
via MITRE·02:14 PM
RemedyDescriptionWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-1496?

CVE-2026-1496 is classified as a high-severity vulnerability due to its ability to allow authentication bypass.

2

How do I fix CVE-2026-1496?

To fix CVE-2026-1496, update to the latest version of Synopsys Coverity Connect that addresses this vulnerability.

3

Who is affected by CVE-2026-1496?

CVE-2026-1496 affects users of vulnerable versions of Synopsys Coverity Connect with access to the /token API endpoint.

4

What are the consequences of exploiting CVE-2026-1496?

Exploiting CVE-2026-1496 can lead to unauthorized access to sensitive information and resources within Coverity Connect.

5

Is there a workaround for CVE-2026-1496?

Yes, a temporary workaround for CVE-2026-1496 is to implement network-level security measures to restrict access to the /token API endpoint.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203