Skip to content
Networks

CVE-2026-48131

8.1
High
EPSS 3%May 26, 2026

VPN IKE fragment mishandling may crash the service, causing DoS.

common questions

Is CVE-2026-48131 being exploited?

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

How severe is CVE-2026-48131?

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

Not known from our data. No patch reference has been recorded for CVE-2026-48131, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-48131 affect?

CVE-2026-48131 affects VPN services implementing IKE over UDP 500 (and NAT-T 4500). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48131?

Monitor advisories; apply patch when available.

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

executive summary
technical analysis
affected
VPN services implementing IKE over UDP 500 (and NAT-T 4500)
impact

DoS: unexpected IKE fragment value terminates VPN service, disrupting VPN access.

action required

Monitor only

affected versions
checkpoint Quantum Security Gateway
  • affectedR82.10 with Jumbo Hotfix Take 6 or below
  • affectedR82 with Jumbo Hotfix Take 91 or below
  • affectedR81.20 with Jumbo Hotfix Take 127 or below
  • affectedAll releases from R81.10 and below

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