Black Duck Coverity prior 2025.12.1 API Endpoint /token authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Black Duck Coverity up to 2024.12.1/2025.3.1/2025.6.3/2025.9.2/2025.12.0. It has been rated as critical. Affected is an unknown function of the file /token of the component API Endpoint. Performing a manipulation results in authorization. This vulnerability was named CVE-2026-1496. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability was found in Black Duck Coverity up to 2024.12.1/2025.3.1/2025.6.3/2025.9.2/2025.12.0. It has been classified as critical. This affects an unknown function of the file /token of the component API Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was presented by Huong Kieu. The advisory is shared at community.blackduck.com. This vulnerability is uniquely identified as CVE-2026-1496 since 01/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
Upgrading to version 2024.3.0A, 2024.3.1A, 2024.3.2A, 2024.6.0A, 2024.6.1A, 2024.9.0A, 2024.9.1A, 2024.12.0A, 2024.12.1A, 2024.12.2, 2025.3.0A, 2025.3.1A, 2025.3.2, 2025.6.0A, 2025.6.2A, 2025.6.4, 2025.9.0A, 2025.9.2A, 2025.9.3, 2025.12.0, 2025.12.0A or 2025.12.1 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 2024.12.0
- 2024.12.1
- 2025.0
- 2025.1
- 2025.2
- 2025.3
- 2025.3.0
- 2025.3.1
- 2025.4
- 2025.5
- 2025.6
- 2025.6.0
- 2025.6.1
- 2025.6.2
- 2025.6.3
- 2025.7
- 2025.8
- 2025.9
- 2025.9.0
- 2025.9.1
- 2025.9.2
- 2025.10
- 2025.11
- 2025.12.0
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Coverity 2024.3.0A/2024.3.1A/2024.3.2A/2024.6.0A/2024.6.1A/2024.9.0A/2024.9.1A/2024.12.0A/2024.12.1A/2024.12.2/2025.3.0A/2025.3.1A/2025.3.2/2025.6.0A/2025.6.2A/2025.6.4/2025.9.0A/2025.9.2A/2025.9.3/2025.12.0/2025.12.0A/2025.12.1
Timeline
01/27/2026 CVE reserved03/27/2026 Advisory disclosed
03/27/2026 VulDB entry created
03/27/2026 VulDB entry last update
Sources
Advisory: community.blackduck.comResearcher: Huong Kieu
Status: Confirmed
CVE: CVE-2026-1496 (🔒)
GCVE (CVE): GCVE-0-2026-1496
GCVE (VulDB): GCVE-100-353913
Entry
Created: 03/27/2026 15:43Changes: 03/27/2026 15:43 (68)
Complete: 🔍
Cache ID: 216:DFF:103
No comments yet. Languages: en.
Please log in to comment.