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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Black Duck Coverity
Default version status: unaffected
2024.3.0 to < 2025.12.0affected2024.3.0Aunaffected2024.3.1Aunaffected2024.3.2Aunaffected2024.6.0Aunaffected2024.6.1Aunaffected2024.9.0Aunaffected2024.9.1Aunaffected2024.12.0Aunaffected2024.12.1Aunaffected2024.12.2unaffected2025.3.0Aunaffected2025.3.1Aunaffected2025.3.2unaffected2025.6.0Aunaffected2025.6.2Aunaffected2025.6.4unaffected2025.9.0Aunaffected2025.9.2Aunaffected2025.9.3unaffected2025.12.0Aunaffected2025.12.1unaffected
References
- 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 ↗