Skip to content
Systems

CVE-2026-72462

8.8
High
EPSS 0.13%Patch availableAug 17, 2026

AppArmor unix-socket race may allow policy bypass or unauthorized socket access

common questions

Is CVE-2026-72462 being exploited?

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

How severe is CVE-2026-72462?

CVE-2026-72462 is rated High with a CVSS score of 8.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-72462?

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

What does CVE-2026-72462 affect?

CVE-2026-72462 affects Linux kernel (AppArmor enabled), Linux distributions using AppArmor (e.g., Ubuntu, SUSE). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72462?

Install vendor kernel/AppArmor updates and reboot affected hosts.

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

executive summary
technical analysis
affected
Linux kernel (AppArmor enabled)Linux distributions using AppArmor (e.g., Ubuntu, SUSE)
impact

Local attacker can race AppArmor unix-socket mediation to bypass policy, access restricted sockets or escalate privileges.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= bc6e5f6933b8e7b74858ac830d5b9b4ca10a099a and < d8ea44f6090c087fe255d9512fb808574b4d88e8
  • affected>= bc6e5f6933b8e7b74858ac830d5b9b4ca10a099a and < d680472db98823d90fc91362910901e468269318
  • affected>= bc6e5f6933b8e7b74858ac830d5b9b4ca10a099a and < b1aea2c1960771a276d7e68c7424168eccd0c3da
  • affected6.17
vendor says fixed in< 6.17, >= 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