Skip to content
major vulnerability· requires attention

Widely deployed enterprise tool; critical auth bypass enables full account takeover; high risk across orgs.

Applications

CVE-2026-1496

9.3
Critical
EPSS 0.48%Mar 28, 2026

Auth bypass in Coverity Connect via /token; full account takeover.

common questions

Is CVE-2026-1496 being exploited?

Not confirmed. CVE-2026-1496 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.

How severe is CVE-2026-1496?

CVE-2026-1496 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-1496?

Not known from our data. No patch reference has been recorded for CVE-2026-1496, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-1496 affect?

CVE-2026-1496 affects Coverity Connect. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-1496?

Patch when available; restrict/monitor token endpoint.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Coverity Connect
impact

Authentication bypass via /token; attacker can assume all roles of a valid user; full account takeover.

action required

Immediate action required

affected versions
Black Duck Coverity
  • affected>= 2024.3.0 and < 2025.12.0
vendor says fixed in2024.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.0A, 2025.12.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free