PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-78133 strongSwan CVE debrief

A use-after-free vulnerability exists in libcharon of strongSwan versions 6.0.0 through 6.0.7, which can be triggered during IKEv2 rekeying collision handling. This issue has been addressed in version 6.1.0. The vulnerability affects the libcharon component and requires immediate attention from network administrators and security teams to verify exposure and apply patches or mitigations. The issue is a high-severity vulnerability that could lead to potential remote code execution or denial of service, and possible disruption of VPN services.

Vendor
strongSwan
Product
Unknown
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-11
Original CVE updated
2026-09-14
Advisory published
2026-09-11
Advisory updated
2026-09-14

Who should care

Network administrators and security teams responsible for strongSwan deployments, particularly those using IKEv2, should assess exposure and apply necessary patches or mitigations.

Why it matters

CVE-2026-78133 is a high-severity vulnerability in strongSwan's libcharon, affecting versions 6.0.0-6.0.7. It requires immediate attention from network administrators and security teams to verify exposure and apply patches.

  • Potential remote code execution or denial of service.
  • Possible disruption of VPN services.
  • Need for verification of affected versions in inventory.
  • Priority for patching or upgrading to version 6.1.0.

Technical summary

The libcharon component in strongSwan versions 6.0.0 through 6.0.7 contains a use-after-free vulnerability that can occur during IKEv2 rekeying collision handling. This issue has been fixed in version 6.1.0. The vulnerability is a high-severity issue that requires immediate attention from network administrators and security teams to verify exposure and apply patches or mitigations. The technical details of the vulnerability are based on official CVE Program records and NIST NVD detail pages.

Defensive priority

Defenders should prioritize verifying exposure and applying patches for strongSwan versions 6.0.0 through 6.0.7.

Recommended defensive actions

  • Verify if strongSwan versions 6.0.0 through 6.0.7 are in use and apply patches or upgrades to version 6.1.0 or later.
  • Review IKEv2 rekeying configurations and consider implementing additional security measures.
  • Monitor for potential exploitation attempts and update intrusion detection systems.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and affected versions. The vulnerability has been confirmed in strongSwan versions 6.0.0 through 6.0.7, and defenders should verify exposure and apply patches or upgrades to version 6.1.0 or later. The evidence is based on official CVE Program records and NIST NVD detail pages, which provide source-provided CVE metadata and source-specific vulnerability assessments.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-78133 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-78133

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-78133 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-78133

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://github.com/strongswan/strongswan/releases/tag/6.1.0

    [email protected] - Patch, Release Notes, Vendor Advisory

  • Source reference

    Unverified legacy reference

    URL: https://www.strongswan.org/blog/2026/09/07/strongswan-vulnerability-(cve-2026-78133).html

    [email protected] - Mitigation, Vendor Advisory

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.