# CVE-2026-8668: Hardcoded credentials in embedded content

> Hardcoded credentials in Chef 360 allowed unauthenticated access to internal message queues containing tenant identifiers.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:H/SI:N/SA:L/E:P/S:N/AU:Y/RE:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-2q9w-rh4f-g84j

## What is CVE-2026-8668?

CVE-2026-8668 is a low-severity vulnerability in Progress Chef Chef360, published on 18 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-523 (Unprotected Transport of Credentials)

## Which versions are affected by CVE-2026-8668?


## How do I fix CVE-2026-8668?

No fix has been published for CVE-2026-8668 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8668 being exploited?

There is no known exploitation of CVE-2026-8668 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8668 and fix it if it is affected.

What it is: CVE-2026-8668 is a low-severity vulnerability in Progress Chef Chef360, published on 18 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8668 in the wild and no public exploit code.

Affected product: Progress Chef Chef360. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8668/ (Markdown: https://insights.sbomify.com/CVE-2026-8668/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8668
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8668
- OSV: https://osv.dev/vulnerability/CVE-2026-8668

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8668/
Summaries are generated and may contain mistakes; the official description above is the record.