CVE-2026-55567

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

BleachBit cleans files to free disk space and to maintain privacy. Prior to 6.0.1, privileged Windows cleaning does not lock and validate a target's parent directory before deletion. A local unprivileged user can replace that directory with a Windows junction and use a native symlink to redirect the elevated deletion to an attacker-selected file. The arbitrary privileged file deletion can be combined with Windows Installer behavior to obtain local SYSTEM privileges. This issue is fixed in version 6.0.1.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 21, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v6.0.1 beta

Patch available: bleachbit/bleachbit v6.0.1 (pre-release)

https://github.com/bleachbit/bleachbit/releases/tag/v6.0.1
github_commit

commit ee128238e92c (bleachbit/bleachbit)

Fix landed in bleachbit/bleachbit commit ee128238e92c — awaiting tagged release

https://github.com/bleachbit/bleachbit/commit/ee128238e92c7192f0c4d6406b1bd0cd9155e7e0
github_pr

fix: safely delete a file

Upstream fix in progress (PR #1774 · bleachbit/bleachbit, state=closed)

https://github.com/bleachbit/bleachbit/pull/1774
github Patch Available🟡 PoC Available

Exploit File Delete to Escalate Privilege in BleachBit · Advisory · bleachbit/bleachbit · GitHub

https://github.com/bleachbit/bleachbit/security/advisories/GHSA-vcjw-px28-5w94

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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.

  1. 2026-09-24 20:04 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-23 19:08 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 17:23 UTCEG score recompute
  6. 2026-09-21 15:22 UTCEG score recompute
  7. 2026-09-21 14:25 UTCEG score recompute
  8. 2026-09-21 14:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55567?
CVE-2026-55567 is a high vulnerability published on September 21, 2026. BleachBit cleans files to free disk space and to maintain privacy. Prior to 6.0.1, privileged Windows cleaning does not lock and validate a target's parent directory before deletion. A local unprivileged user can replace that directory with a Windows junction and use a native symlink to redirect…
When was CVE-2026-55567 disclosed?
CVE-2026-55567 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55567 actively exploited?
CVE-2026-55567 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-55567?
CVE-2026-55567 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-55567?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55567, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55567?

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