Skip to main content
Mallory
UnratedVulnerability

CVE-2026-101318: FreeBSD IPsec ESP IV Reuse

Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-101318CWE-323

CVE-2026-101318 is a concurrency vulnerability in FreeBSD's IPsec ESP implementation affecting Security Associations using AES-CTR, AES-GCM, or ChaCha20-Poly1305. The esp_output() function increments the per-Security Association initialization-vector counter while holding the Security Association lock in shared mode. Concurrent packet transmissions on different CPUs can consequently receive identical counter values, causing encryption of multiple packets with the same IV and key. This reuse can allow an on-path attacker to modify intercepted packets without detection and potentially recover plaintext.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

The vulnerability compromises the confidentiality and integrity of affected IPsec traffic. An on-path attacker may recover plaintext from packets sharing an IV and key and may modify intercepted packets without detection. Previously reused IVs may permit continued packet forgery after patching if affected Security Associations retain their keys.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available. Systems not using IPsec, or whose Security Associations do not use AES-CTR, AES-GCM, or ChaCha20-Poly1305, are not affected.

Remediation

Patch, then assume compromise.

Upgrade to a corrected FreeBSD version for the installed branch and reboot. Fixed versions include 15.2-STABLE, 15.1-RELEASE-p7, 14.5-STABLE, 14.5-RELEASE-p4, and 14.4-RELEASE-p13. Corresponding fixed FreeBSD-kernel package versions are 15.1_7, 14.5_4, and 14.4_13, or later patched versions. Eligible base-package installations can use 'pkg upgrade -r FreeBSD-base'; eligible binary-distribution installations can use 'freebsd-update fetch' followed by 'freebsd-update install'. Alternatively, verify and apply the official source patch, rebuild the kernel, and reboot. Assign new keys to manually keyed Security Associations to prevent continued exploitation of previously reused IVs. IKE-negotiated Security Associations are replaced during reboot.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-101318 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-101318 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-101318?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-101318.
Is there a patch for CVE-2026-101318?
Upgrade to a corrected FreeBSD version for the installed branch and reboot. Fixed versions include 15.2-STABLE, 15.1-RELEASE-p7, 14.5-STABLE, 14.5-RELEASE-p4, and 14.4-RELEASE-p13.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.