Skip to main content
VulnerabilityPublished

CVE-2026-1496: Black Duck Coverity · Insecure Direct Object Reference

Affects Black Duck CoveritySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 2025.12.0 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2025.12.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Black Duck Coverity to 2025.12.0.

Affected software

ProductAffectedFixed in
Black DuckCoverityAffected
  • >=2024.3.0 <2025.12.0
Fixed in
  • 2025.12.0
GitHubblackduck-inc/Coverity-Usage-Log-Analyzerpkg:github/blackduck-inc/Coverity-Usage-Log-AnalyzerOther threatsAffected
  • =2024.3.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-1496, organizations should immediately restrict access to the /token API endpoint by implementing network-level controls such as IP whitelisting, VPN-only access, or firewall rules to limit exposure to trusted users and systems. Employ strong monitoring and logging of all requests to the /token endpoint to detect unusual or repeated access attempts, especially those involving invalid or guessed usernames. If you cannot patch yet, consider disabling command line tooling that interacts with the /token endpoint if feasible, or isolate the Coverity Connect instance in a segmented network environment. Enforce strict user account management policies, including the use of least privilege principles and regular review of user roles and permissions. Additionally, implement multi-factor authentication (MFA) for Coverity Connect user accounts if supported, to reduce the impact of compromised credentials. Stay informed on vendor advisories and apply patches promptly once available. Conduct thorough security assessments of the Coverity Connect deployment to identify and remediate any other potential weaknesses. Finally, educate development and security teams about this vulnerability to ensure rapid detection and response to any suspicious activity.

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.

References

Community reviews

Loading reviews…