PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-78134 strongSwan CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-09-11T02:18:34.910Z and has not been modified since then. The vulnerability affects strongSwan 4.5.0 through 6.0.7, with Incorrect Access Control in the eap-ttls and eap-peap plugins due to missing or mismatched inner EAP identity. Network administrators and security teams should assess exposure and prioritize verification of vulnerable strongSwan deployments. The CVE has a CVSS score of 7.1 and is considered HIGH severity.

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

Who should care

Network administrators and security teams responsible for strongSwan deployments should assess exposure and prioritize verification of vulnerable strongSwan versions (4.5.0 through 6.0.7). They should also monitor for potential unauthorized access attempts and prioritize remediation for deployments using affected versions.

Why it matters

CVE-2026-78134 has a CVSS score of 7.1 and is considered HIGH severity. It affects strongSwan 4.5.0 through 6.0.7, with Incorrect Access Control in the eap-ttls and eap-peap plugins. Network administrators and security teams should assess exposure and prioritize verification of vulnerable deployments.

  • Verification of vulnerable strongSwan versions in inventory is required
  • Potential unauthorized access attempts may need to be monitored and mitigated
  • Remediation priority is high for deployments using affected versions

Technical summary

CVE-2026-78134 affects strongSwan 4.5.0 through 6.0.7, with Incorrect Access Control in the eap-ttls and eap-peap plugins due to missing or mismatched inner EAP identity. The vulnerability has a CVSS score of 7.1 and is considered HIGH severity. Network administrators and security teams should assess exposure and prioritize verification of vulnerable strongSwan deployments.

Defensive priority

Network administrators and security teams should assess exposure and prioritize verification of vulnerable strongSwan deployments.

Recommended defensive actions

  • Assess exposure of strongSwan deployments to CVE-2026-78134
  • Verify vulnerable versions (4.5.0 through 6.0.7) in inventory
  • Monitor for potential unauthorized access attempts

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in strongSwan 4.5.0 through 6.0.7, but specific version remediation details are limited.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-78134 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-78134 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

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

Supplemental references

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.