CVE-2026-8338

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
9.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.2Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Black Duck Software, Inc.) lists Black Duck Coverity Connect versions 2023.6.0 up to but not including 2026.6.0 as affected. No release containing a fix is confirmed on record.

A Spring Security authentication and authorization bypass exists in Coverity Connect versions between 2023.6.0 and 2026.3.0. An unauthenticated malicious threat actor that can send a specially crafted HTTP request is able to bypass authentication and authorization controls on certain API endpoints to access data within Coverity.

CVSS v3
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Sep 15, 2026
No fix on record yet.
Web page

Black Duck Community

https://community.blackduck.com/s/article/Black-Duck-Product-Security-Advisory-CVE-2026-8338-Authentication-and-Authorization-Bypass

Vendor Advisories for CVE-2026-8338(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 88× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 420 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 321 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-20 02:14 UTCEG score recompute
  2. 2026-10-20 02:13 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  3. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-19 01:32 UTCEG score recompute
  5. 2026-10-19 01:32 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  6. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-18 03:46 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  8. 2026-10-18 03:07 UTCEG score recompute
  9. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-17 06:00 UTCEG score recompute
  11. 2026-10-17 05:59 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  12. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-16 07:07 UTCEG score recompute
  14. 2026-10-16 07:07 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  15. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-15 05:54 UTCEG score recompute
  17. 2026-10-15 05:54 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  18. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-10-14 01:32 UTCEG score recompute
  20. 2026-10-14 01:32 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  21. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-10-12 21:43 UTCEG score recompute
  23. 2026-10-12 21:43 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  24. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-12 14:54 UTCEG score recompute
Show 74 more
  1. 2026-10-12 05:18 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  2. 2026-10-11 19:19 UTCEG score recompute
  3. 2026-10-11 16:35 UTCEG score recompute
  4. 2026-10-11 13:53 UTCEG score recompute
  5. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-07 04:13 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  11. 2026-10-07 00:00 UTCEG score recompute
  12. 2026-10-07 00:00 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-05 20:51 UTCEG score recompute
  15. 2026-10-05 20:51 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  16. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-05 02:36 UTCEG score recompute
  18. 2026-10-05 02:36 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-04 12:34 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  21. 2026-10-04 07:01 UTCEG score recompute
  22. 2026-10-04 07:01 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  23. 2026-10-03 03:11 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  24. 2026-10-02 17:57 UTCEG score recompute
  25. 2026-10-02 17:57 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  26. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-10-01 16:25 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  28. 2026-10-01 12:12 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  29. 2026-10-01 07:46 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  30. 2026-10-01 03:34 UTCEG score recompute
  31. 2026-10-01 03:33 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  32. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-09-29 07:35 UTCEG score recompute
  34. 2026-09-29 07:35 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  35. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-09-28 12:54 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  37. 2026-09-28 07:26 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  38. 2026-09-28 03:13 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  39. 2026-09-27 19:37 UTCEG score recompute
  40. 2026-09-27 19:37 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  41. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  42. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  43. 2026-09-25 09:51 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  44. 2026-09-25 05:38 UTCEG score recompute
  45. 2026-09-25 05:38 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  46. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  47. 2026-09-24 10:29 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  48. 2026-09-24 06:16 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  49. 2026-09-24 02:03 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  50. 2026-09-23 21:48 UTCEG score recompute
  51. 2026-09-23 21:48 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  52. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  53. 2026-09-23 10:17 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  54. 2026-09-23 06:03 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  55. 2026-09-23 01:50 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  56. 2026-09-22 21:37 UTCEG score recompute
  57. 2026-09-22 21:37 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  58. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  59. 2026-09-22 15:48 UTCEG score recompute
  60. 2026-09-22 15:48 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  61. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  62. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  63. 2026-09-20 11:16 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  64. 2026-09-20 04:36 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  65. 2026-09-20 00:22 UTCEG score recompute
  66. 2026-09-20 00:22 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  67. 2026-09-19 04:53 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  68. 2026-09-19 00:05 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  69. 2026-09-18 19:34 UTCEG score recompute
  70. 2026-09-18 19:33 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  71. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  72. 2026-09-18 15:16 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  73. 2026-09-18 10:07 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL
  74. 2026-09-18 05:54 UTCGHSA enrichmentGHSA-f3gv-992v-c3v5 · GitHub severity CRITICAL

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8338?
CVE-2026-8338 is a critical-severity vulnerability; its CVE record was published on July 29, 2026. A Spring Security authentication and authorization bypass exists in Coverity Connect versions between 2023.6.0 and 2026.3.0. An unauthenticated malicious threat actor that can send a specially crafted HTTP request is able to bypass authentication and authorization controls on certain API endpoints…
When was the CVE record for CVE-2026-8338 published?
The CVE record for CVE-2026-8338 was published on July 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-8338 actively exploited?
CVE-2026-8338 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8338?
CVE-2026-8338 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-8338?
No fix for CVE-2026-8338 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Black Duck Software, Inc.) lists Black Duck Coverity Connect versions 2023.6.0 up to but not including 2026.6.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-8338 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-8338?

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

Book a Demo →Browse All CVEs