CVE-2026-8668

LOWPre-NVD 2.32.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% 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
Trending — 3 sources updated this week
2.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.3Exploit: NoneExposed: 0

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

A static credential embedded in Chef 360 prior to v1.7.0 permitted unauthenticated access to internal message queues.  Queue messages contained tenant-specific identifiers.  The credential has been rotated and replaced with per-tenant access in subsequent versions, eliminating this access method entirely.

CVSS v3
2.3
EG Score
2.3(medium)
EPSS
6.7%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 22, 2026

References (1)

Vendor Advisories for CVE-2026-8668(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 14× in last 7d / 29× 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-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 09:32 UTCEG score recompute
  6. 2026-07-05 09:32 UTCGHSA enrichment
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-02 02:41 UTCEG score recompute
  12. 2026-07-02 02:41 UTCGHSA enrichment
  13. 2026-07-01 15:07 UTCEPSS rescore
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-28 19:52 UTCEG score recompute
  17. 2026-06-28 19:52 UTCGHSA enrichment
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-25 13:50 UTCEPSS rescore
  22. 2026-06-25 13:03 UTCEG score recompute
  23. 2026-06-25 13:03 UTCGHSA enrichment
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
Show 4 more
  1. 2026-06-22 06:13 UTCEG score recompute
  2. 2026-06-22 06:13 UTCGHSA enrichment
  3. 2026-06-18 23:24 UTCEG score recompute
  4. 2026-06-18 23:22 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-8668?
CVE-2026-8668 is a low vulnerability published on June 18, 2026. A static credential embedded in Chef 360 prior to v1.7.0 permitted unauthenticated access to internal message queues. Queue messages contained tenant-specific identifiers. The credential has been rotated and replaced with per-tenant access in subsequent versions, eliminating this access method…
When was CVE-2026-8668 disclosed?
CVE-2026-8668 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8668 actively exploited?
CVE-2026-8668 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-8668?
CVE-2026-8668 has a CVSS v3 base score of 2.3 (NVD).
How do I remediate CVE-2026-8668?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8668, 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-8668

Explore →

Is Your Infrastructure Affected by CVE-2026-8668?

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

Start Free Scan →Browse All CVEs