CVE-2025-11568

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.4 from GitHub Security Advisory published 2025-10-15. A secondary CVSS source baseline 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A data corruption vulnerability has been identified in the luksmeta utility when used with the LUKS1 disk encryption format. An attacker with the necessary permissions can exploit this flaw by writing a large amount of metadata to an encrypted device. The utility fails to correctly validate the available space, causing the metadata to overwrite and corrupt the user's encrypted data. This action leads to a permanent loss of the stored information. Devices using the LUKS formats other than LUKS1 are not affected by this issue.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

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 (value × EchelonGraph’s weight)
Severity44% × 45%
The EG Score, 4.4 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
below the 1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 15, 2025

Last Modified

September 1, 2026

Advisory Details (6)

Auto-updated Jun 27, 2026
Patch available. Sources: redhat, github_pr.
GitHub pull request Patch Available

Fix handling of large metadata

Patch available: latchset/luksmeta v10 (PR #16 merged 2025-10-31)

https://github.com/latchset/luksmeta/pull/16
Red HatMentions a patch (unverified)

2404244 – (CVE-2025-11568) CVE-2025-11568 luksmeta: Data corruption when handling LUKS1 partitions with luksmeta

Affected: Red Hat Enterprise Linux 8

https://bugzilla.redhat.com/show_bug.cgi?id=2404244
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2025-11568
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:18824
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:18421
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2025:23086

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatluksmeta-0:10-1.el92026-05-19redhat
redhatluksmeta-0:10-1.el102026-05-19redhat
redhatluksmeta-0:9-4.el8_10.12025-12-11redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
luksmeta10-1, 9-3, 9-4
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
luksmeta9-4
  • every version up to 9-4+deb12u1: fixed in 9-4+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
luksmeta9-4
  • every version up to 9-4+deb13u1: fixed in 9-4+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
luksmeta9-4
  • every version up to 10-1: fixed in 10-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 90 of 181 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 10 repeat rows among the latest 100 are merged into the row they repeat. The 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  2. 2026-10-12 17:26 UTCEG score recompute
  3. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  4. 2026-10-11 20:56 UTCEG score recompute
  5. 2026-10-11 19:06 UTCEG score recompute
  6. 2026-10-11 15:47 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  9. 2026-10-10 00:55 UTCOSV refresh
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  11. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  16. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  17. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  18. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  19. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  20. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-20 09:03 UTCOSV refresh
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-09-15 03:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
Show 65 more
  1. 2026-09-12 14:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-09-11 14:51 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-09-11 09:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-09-10 09:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-09-07 16:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-09-06 13:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-09-04 13:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-09-04 05:05 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-09-02 14:10 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-09-01 13:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-09-01 12:30 UTCEG score recompute
  12. 2026-09-01 12:30 UTCVendor advisory
  13. 2026-09-01 12:30 UTCGHSA enrichmentGHSA-pvmm-7c2r-wmp4 · GitHub CVSS 4.4
  14. 2026-09-01 12:02 UTCEG score recompute
  15. 2026-09-01 12:02 UTCVendor advisory
  16. 2026-09-01 12:02 UTCGHSA enrichmentGHSA-pvmm-7c2r-wmp4 · GitHub CVSS 4.4
  17. 2026-08-31 16:43 UTCEG score recompute
  18. 2026-08-31 16:43 UTCVendor advisory
  19. 2026-08-31 16:43 UTCGHSA enrichmentGHSA-pvmm-7c2r-wmp4 · GitHub CVSS 4.4
  20. 2026-08-31 15:09 UTCEG score recompute
  21. 2026-08-31 15:09 UTCVendor advisory
  22. 2026-08-31 15:09 UTCGHSA enrichmentGHSA-pvmm-7c2r-wmp4 · GitHub CVSS 4.4
  23. 2026-08-30 19:16 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-08-30 01:21 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  25. 2026-08-28 21:39 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  26. 2026-08-27 14:24 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  27. 2026-08-26 14:44 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  28. 2026-08-25 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  29. 2026-08-24 14:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  30. 2026-08-21 23:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  31. 2026-08-21 13:23 UTCEG score recompute
  32. 2026-08-21 13:23 UTCVendor advisory
  33. 2026-08-21 13:23 UTCGHSA enrichmentGHSA-pvmm-7c2r-wmp4 · GitHub CVSS 4.4
  34. 2026-08-21 12:50 UTCEG score recompute
  35. 2026-08-21 12:50 UTCVendor advisory
  36. 2026-08-21 12:50 UTCGHSA enrichmentGHSA-pvmm-7c2r-wmp4 · GitHub CVSS 4.4
  37. 2026-08-20 22:54 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  38. 2026-08-18 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  39. 2026-08-17 13:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  40. 2026-08-16 14:55 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  41. 2026-08-16 02:13 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  42. 2026-08-15 01:29 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  43. 2026-08-12 04:04 UTCOSV refresh
  44. 2026-08-08 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  45. 2026-08-07 16:26 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  46. 2026-08-06 13:45 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  47. 2026-08-05 19:16 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  48. 2026-08-04 15:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  49. 2026-08-03 10:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  50. 2026-08-01 04:14 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  51. 2026-07-30 16:26 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  52. 2026-07-30 01:29 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  53. 2026-07-28 15:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  54. 2026-07-27 14:12 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  55. 2026-07-27 09:39 UTCOSV refresh
  56. 2026-07-25 14:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  57. 2026-07-23 02:48 UTCEG score recompute
  58. 2026-07-22 14:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  59. 2026-07-20 17:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  60. 2026-07-19 14:30 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  61. 2026-07-18 10:03 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  62. 2026-07-16 17:02 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  63. 2026-07-15 16:57 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  64. 2026-07-13 22:29 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  65. 2026-07-13 06:12 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile

Frequently asked(5)

What is CVE-2025-11568?
CVE-2025-11568 is a medium-severity vulnerability; its CVE record was published on October 15, 2025. A data corruption vulnerability has been identified in the luksmeta utility when used with the LUKS1 disk encryption format. An attacker with the necessary permissions can exploit this flaw by writing a large amount of metadata to an encrypted device. The utility fails to correctly validate the…
When was CVE-2025-11568 made public?
CVE-2025-11568 was made public on October 14, 2025: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 15, 2025. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2025-11568 actively exploited?
CVE-2025-11568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-11568?
CVE-2025-11568 has a CVSS base score of 4.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-11568?
A fix for CVE-2025-11568 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-11568 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-11568

Explore →

Is Your Infrastructure Affected by CVE-2025-11568?

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