CVE-2026-8100: High severity Chef Chef 360 vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Chef 360to a version that resolves this vulnerability.Fixed in 1.7.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-8100?
The severity of CVE-2026-8100 is rated as high with a score of 8.6.
What is the impact of CVE-2026-8100?
CVE-2026-8100 can lead to unauthorized access to protected API endpoints due to improper handling of URL-encoded paths.
How do I fix CVE-2026-8100?
To fix CVE-2026-8100, apply the latest updates or patches provided by Chef for Chef 360.
Who is affected by CVE-2026-8100?
CVE-2026-8100 affects users of Chef 360 who utilize the API endpoints.
When was CVE-2026-8100 published?
CVE-2026-8100 was published on June 18, 2026.