CVE-2026-78395

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

GHSA-57vw-f9g4-3923 ↗EUVD-2026-112612 ↗

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.
Link Library < 7.10.0
fixed in 7.10.0
ETK-2026-2948Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 04h 57msince last run
33mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h20m
0
+4h
+6h
+8h
+10h
+12h

description

Link Library versions before 7.10.0 are affected by an authorization check bypass in front-end link submission. An unauthenticated attacker may submit links to a library configured to require login when another library permits unauthenticated submissions and its form token is available.

mitigation

Upgrade Link Library to version 7.10.0 or later. Until upgrading, disable public link submissions or ensure all libraries use consistent login requirements.

fixed in 7.10.0

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.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
33m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 06:00Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-29 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-29 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2948",
  "cve_id": "CVE-2026-78395",
  "display_id": "CVE-2026-78395",
  "ghsa_id": "GHSA-57vw-f9g4-3923",
  "euvd_id": "EUVD-2026-112612",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Login-requirement bypass in Link Library",
  "summary": "Link Library versions before 7.10.0 are affected by an authorization check bypass in front-end link submission. An unauthenticated attacker may submit links to a library configured to require login when another library permits unauthenticated submissions and its form token is available.",
  "mitigation": "Upgrade Link Library to version 7.10.0 or later. Until upgrading, disable public link submissions or ensure all libraries use consistent login requirements.",
  "vendor": null,
  "product": "Link Library",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 7.10.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.10.0"
      ],
      "package_name": "Link Library",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 33.21820291666667,
  "t0_at": "2026-10-29T06:00:22.791000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T06:00:22.791000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T06:00:22.791000+00:00",
      "url": "https://github.com/advisories/GHSA-57vw-f9g4-3923"
    }
  }
}

published 2026-10-29 07:47Z
last change 2026-10-30 09:38Z

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.