CVE-2026-8100

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 56% 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
8.6EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.6Exploit: None knownExposed services: Not assessed

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

Impact

A security issue has been identified in Chef 360 that could allow unauthorized access to protected API endpoints under specific conditions. This issue is due to improper handling of URL-encoded paths during request processing. In certain scenarios, an authenticated request may bypass standard access controls gaining additional privileges, potentially allowing access to API endpoints that are intended to be restricted to higher-permissioned roles. The impact is limited to environments where the affected request patterns can be triggered and depends on specific deployment configuration and access controls in place. Resolution The issue has been addressed through product updates that improve request validation and enforce strict path normalization before authorization checks.  Customers are advised to update to the latest available version containing the fix, version 1.7.1 or later.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
43
EG Risk 43/100

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
Severity86% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

Published

June 18, 2026

Last Modified

June 22, 2026

Advisory Details (1)

Auto-updated Jun 18, 2026
No fix on record yet.
generic

Progress Customer Community

https://community.progress.com/s/article/Authentication-Bypass-via-URL-Encoded-Path-Traversal

Vendor Advisories for CVE-2026-8100(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 7× in last 7d / 30× 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.

Showing the most recent 100 of 245 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8100?
CVE-2026-8100 is a high vulnerability published on June 18, 2026. Impact A security issue has been identified in Chef 360 that could allow unauthorized access to protected API endpoints under specific conditions. This issue is due to improper handling of URL-encoded paths during request processing. In certain scenarios, an authenticated request may bypass…
When was CVE-2026-8100 disclosed?
CVE-2026-8100 was first published 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-8100 actively exploited?
CVE-2026-8100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8100?
CVE-2026-8100 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-8100?
No fix for CVE-2026-8100 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 vendor advisories EchelonGraph has for CVE-2026-8100 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-8100?

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

Book a Demo →Browse All CVEs