CVE-2026-1496

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
47(Track)
EG Risk 47/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

March 27, 2026

Last Modified

June 17, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:14 UTCEPSS rescore
  4. 2026-09-13 16:46 UTCEPSS rescore
  5. 2026-09-12 15:00 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-11 09:36 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:48 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 66 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 10:00 UTCEG score recompute
  5. 2026-08-16 10:00 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 23:25 UTCGHSA enrichment
  9. 2026-08-14 19:13 UTCGHSA enrichment
  10. 2026-08-14 14:44 UTCGHSA enrichment
  11. 2026-08-14 10:32 UTCGHSA enrichment
  12. 2026-08-14 06:19 UTCEG score recompute
  13. 2026-08-14 06:19 UTCGHSA enrichment
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 00:50 UTCGHSA enrichment
  16. 2026-08-12 20:37 UTCEG score recompute
  17. 2026-08-12 20:37 UTCGHSA enrichment
  18. 2026-08-12 13:50 UTCEPSS rescore
  19. 2026-08-12 00:57 UTCGHSA enrichment
  20. 2026-08-11 20:45 UTCEG score recompute
  21. 2026-08-11 20:45 UTCGHSA enrichment
  22. 2026-08-11 13:42 UTCEPSS rescore
  23. 2026-08-11 08:01 UTCGHSA enrichment
  24. 2026-08-11 03:48 UTCEG score recompute
  25. 2026-08-11 03:48 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 10:28 UTCGHSA enrichment
  28. 2026-08-10 06:16 UTCGHSA enrichment
  29. 2026-08-10 01:57 UTCGHSA enrichment
  30. 2026-08-09 21:30 UTCGHSA enrichment
  31. 2026-08-09 17:17 UTCEG score recompute
  32. 2026-08-09 17:17 UTCGHSA enrichment
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 13:05 UTCGHSA enrichment
  35. 2026-08-09 05:52 UTCEG score recompute
  36. 2026-08-09 05:52 UTCGHSA enrichment
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-08 09:09 UTCGHSA enrichment
  39. 2026-08-08 04:57 UTCGHSA enrichment
  40. 2026-08-08 00:44 UTCGHSA enrichment
  41. 2026-08-07 20:32 UTCEG score recompute
  42. 2026-08-07 20:32 UTCGHSA enrichment
  43. 2026-08-07 16:19 UTCGHSA enrichment
  44. 2026-08-06 18:43 UTCEG score recompute
  45. 2026-08-06 18:43 UTCGHSA enrichment
  46. 2026-08-06 13:46 UTCEPSS rescore
  47. 2026-08-06 09:20 UTCGHSA enrichment
  48. 2026-08-06 05:00 UTCGHSA enrichment
  49. 2026-08-06 00:47 UTCEG score recompute
  50. 2026-08-06 00:47 UTCGHSA enrichment
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 10:38 UTCEPSS rescore
  54. 2026-08-04 03:57 UTCGHSA enrichment
  55. 2026-08-03 23:09 UTCEG score recompute
  56. 2026-08-03 23:09 UTCGHSA enrichment
  57. 2026-08-03 10:35 UTCEPSS rescore
  58. 2026-08-02 23:37 UTCGHSA enrichment
  59. 2026-08-02 19:25 UTCGHSA enrichment
  60. 2026-08-02 15:12 UTCEG score recompute
  61. 2026-08-02 15:12 UTCGHSA enrichment
  62. 2026-08-02 02:26 UTCEPSS rescore
  63. 2026-08-01 04:15 UTCEPSS rescore
  64. 2026-07-30 01:30 UTCEPSS rescore
  65. 2026-07-27 14:19 UTCEG score recompute
  66. 2026-07-27 14:19 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-1496?
CVE-2026-1496 is a critical vulnerability published on March 27, 2026. 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…
When was CVE-2026-1496 disclosed?
CVE-2026-1496 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1496 actively exploited?
CVE-2026-1496 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.6% of all scored CVEs.
What is the CVSS score of CVE-2026-1496?
CVE-2026-1496 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-1496?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1496, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-1496

Explore →

Is Your Infrastructure Affected by CVE-2026-1496?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.