Skip to content
Applications

CVE-2026-47688

8.2
High
EPSS 0.18%Patch availableJul 22, 2026

Unauthenticated remote deletion of AES credentials and power-management tasks in FOG.

common questions

Is CVE-2026-47688 being exploited?

Not confirmed. CVE-2026-47688 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.

How severe is CVE-2026-47688?

CVE-2026-47688 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-47688?

Yes. A fix has been recorded for CVE-2026-47688. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-47688 affect?

CVE-2026-47688 affects FOG (open-source imaging suite) versions before 1.5.10.1832, FOG 1.6.0-beta versions before 1.6.0-beta.2313. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-47688?

Upgrade to 1.5.10.1832 or 1.6.0-beta.2313; restrict client endpoint access and audit affected hosts.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
FOG (open-source imaging suite) versions before 1.5.10.1832FOG 1.6.0-beta versions before 1.6.0-beta.2313
impact

Unauthenticated attacker can remotely wipe host AES encryption credentials and delete all power-management scheduled tasks via a public HTTP GET.

action required

Immediate action required

affected versions
FOGProject fogproject
  • affected< 1.5.10.1832
  • affected< 1.6.0-beta.2313

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free