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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 9.3NVD modified 2026-10-26 21:10
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 4
- https://community.blackduck.com/s/article/Black-Duck-Security-Advisory-CVE-2026-1496
- https://community.blackduck.com/s/article/Instructions-on-how-to-block-token-endpoint-for-Coverity-Connect
- https://community.blackduck.com/s/article/WAF-IDS-IPS-Mitigation-Guidance
- https://github.com/blackduck-inc/Coverity-Usage-Log-Analyzer