Skip to main content
CVE-2025-8868VulnerabilityPublished

CVE-2025-8868: Progress Software Chef Automate · Information Exposure

Affects Progress Software Chef AutomateSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 25% EPSS · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
25.9% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Progress Software Chef AutomateAffected
  • =0
Fixed in–

AI-suggested

European organizations should prioritize immediate patching by upgrading Chef Automate to version 4.13.295 or later, where this vulnerability is addressed. In the absence of an available patch, organizations should implement strict network segmentation to restrict access to Chef Automate's compliance service, limiting it to trusted administrative networks. Employing Web Application Firewalls (WAFs) with SQL injection detection can help mitigate exploitation attempts. Monitoring and logging access to the compliance service should be enhanced to detect anomalous activities, especially those involving the use of known tokens or unusual SQL queries. Organizations should also review and rotate any tokens or credentials associated with Chef Automate to prevent reuse by attackers. Conducting regular security assessments and penetration tests focused on Chef Automate deployments can help identify residual risks. Finally, integrating Chef Automate logs with centralized Security Information and Event Management (SIEM) systems can improve incident detection and response capabilities.

Description

In Progress Chef Automate, versions earlier than 4.13.295, on Linux x86 platform, an authenticated attacker can gain access to Chef Automate restricted functionality in the compliance service via improperly neutralized inputs used in an SQL command using a well-known token.

References

Community reviews

Loading reviews…