Skip to content
Systems

CVE-2026-72033

9.8
Critical
EPSS 0.74%Patch availableAug 17, 2026

OrangeFS truncation leads to out-of-bounds read and kernel crash (DoS).

common questions

Is CVE-2026-72033 being exploited?

Not confirmed. CVE-2026-72033 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.74% probability of exploitation in the next 30 days.

How severe is CVE-2026-72033?

CVE-2026-72033 is rated Critical with a CVSS score of 9.8. 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-72033?

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

What does CVE-2026-72033 affect?

CVE-2026-72033 affects Linux kernel (orangefs module), OrangeFS filesystem/clients, Systems with orangefs enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72033?

Update kernel to patched release or disable the orangefs module until patched.

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

executive summary
technical analysis
affected
Linux kernel (orangefs module)OrangeFS filesystem/clientsSystems with orangefs enabled
impact

Crafted directory entries can trigger 32-bit truncation, causing out-of-bounds read and kernel oops/crash (remote Denial of Service); potential memory disclosure.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 480e3e532e31666a18520a7964bb4095d7a16b9a and < 1679780f482feeb82acb5995587d4fb1d1fe82fd
  • affected>= 480e3e532e31666a18520a7964bb4095d7a16b9a and < a72bbb43689591c9d36e3bb45c2d4e688cf92682
  • affected>= 480e3e532e31666a18520a7964bb4095d7a16b9a and < 36723b28e3293047f087f4501f1ef4ead418dd84
  • affected>= 480e3e532e31666a18520a7964bb4095d7a16b9a and < 07c05601a9a8e5d4481b2a4a16dc0e3c5bc63ad9
  • affected>= 480e3e532e31666a18520a7964bb4095d7a16b9a and < fdf06a1b66ff39664b01c6bb6a2aa98d81e8ebe1
  • affected>= 480e3e532e31666a18520a7964bb4095d7a16b9a and < 82fc886e244c76fadf05ef1958aaf8815478ccde
  • affected>= 480e3e532e31666a18520a7964bb4095d7a16b9a and < e3d325c0bdb7bc5d1b4cc8d8441d79794cd03729
  • affected>= 480e3e532e31666a18520a7964bb4095d7a16b9a and < 18227a6bc98bd0ba96ed3ce9d5b28776a5a28dfc
  • affected4.12
vendor says fixed in< 4.12, >= 5.10.261 and <= 5.10.*, >= 5.15.212 and <= 5.15.*, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

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