CVE-2026-77207

waiting for further signalsZero needs more public information before it can validate it.

GHSA-jf6r-wr9w-j67c ↗EUVD-2026-100749 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
The Libreswan Project libreswan >= 4.7, <= 5.3.2; >= 5.4, <= 5.4
ETK-2026-1855Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 07h 44msince last run
2h 23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+82h27m
0
+2h
+4h
+6h
+8h
+10h

description

Libreswan is affected by a null pointer dereference while processing PKCS#7 data for IKE certificate authentication. An unauthenticated remote peer can cause the service to crash and restart by sending a crafted IKE authentication message; this can be repeated to deny service.

mitigation

No fixed version is identified in the available evidence. Restrict IKE access to trusted peers or networks and monitor for repeated service restarts until an upstream update can be applied.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.34%25th percentile
agent run time
2h 23m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 21:28Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-13 21:28Z
    ghsa: trigger signal, started the run
  2. 2026-10-13 21:28Z

this entry in the feed

GET /api/v1/feed/CVE-2026-77207

{
  "etk_id": "ETK-2026-1855",
  "cve_id": "CVE-2026-77207",
  "display_id": "CVE-2026-77207",
  "ghsa_id": "GHSA-jf6r-wr9w-j67c",
  "euvd_id": "EUVD-2026-100749",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Null pointer dereference in Libreswan PKCS#7 handling",
  "summary": "Libreswan is affected by a null pointer dereference while processing PKCS#7 data for IKE certificate authentication. An unauthenticated remote peer can cause the service to crash and restart by sending a crafted IKE authentication message; this can be repeated to deny service.",
  "mitigation": "No fixed version is identified in the available evidence. Restrict IKE access to trusted peers or networks and monitor for repeated service restarts until an upstream update can be applied.",
  "vendor": "The Libreswan Project",
  "product": "libreswan",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.7, <= 5.3.2",
        ">= 5.4, <= 5.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "libreswan",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0034,
  "epss_percentile": 0.2588,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 143.15946871666668,
  "t0_at": "2026-10-13T21:28:19.219000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-13T21:28:19.219000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T21:28:19.219000+00:00",
      "url": "https://github.com/advisories/GHSA-jf6r-wr9w-j67c"
    }
  }
}

published 2026-10-17 05:32Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.