Skip to content
Systems

CVE-2026-72061

8.8
High
EPSS 0.18%Patch availableAug 17, 2026

Local kernel bug allows altering IPIP/SIT tunnels across network namespaces.

common questions

Is CVE-2026-72061 being exploited?

Not confirmed. CVE-2026-72061 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-72061?

CVE-2026-72061 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-72061?

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

What does CVE-2026-72061 affect?

CVE-2026-72061 affects Linux kernel (net/sit module), IPIP/SIT tunnels, Systems using network namespaces (containers, VMs). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72061?

Apply Linux kernel updates and restrict CAP_NET_ADMIN capability.

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

executive summary
technical analysis
affected
Linux kernel (net/sit module)IPIP/SIT tunnelsSystems using network namespaces (containers, VMs)
impact

Attacker with CAP_NET_ADMIN in one netns can modify tunnels in another netns, enabling traffic redirection, interception, or network config tampering.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 5e6700b3bf98fe98d630bf9c939ad4c85ce95592 and < cb41b308e9d867725d965b291dd085028e36a480
  • affected>= 5e6700b3bf98fe98d630bf9c939ad4c85ce95592 and < c5a0ae895432596b2f464172da8218e2d84e2932
  • affected>= 5e6700b3bf98fe98d630bf9c939ad4c85ce95592 and < 7d139dec96691cde96cb40ed293e2d13d994fb4f
  • affected>= 5e6700b3bf98fe98d630bf9c939ad4c85ce95592 and < 388ccffbd2e7e5e4271f291085a7451865705305
  • affected>= 5e6700b3bf98fe98d630bf9c939ad4c85ce95592 and < c0ea1aedb37bb979e864ed7787975434bbd9db73
  • affected>= 5e6700b3bf98fe98d630bf9c939ad4c85ce95592 and < 3118e97dae533fb45964b87bbed1801afcff7c65
  • affected>= 5e6700b3bf98fe98d630bf9c939ad4c85ce95592 and < 99ae3248b33df94201915d9c32e7470cdf08cfcd
  • affected>= 5e6700b3bf98fe98d630bf9c939ad4c85ce95592 and < 27ccb68e7cccead5d8c611665a45d23032d468b3
  • affected3.11
vendor says fixed in< 3.11, >= 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