ETK-2026-3778Zero's internal tracking ID, independent of the CVE number.

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

GHSA-q8wp-7gh7-4873 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
other:bindery <= 1.46.2
fixed in 1.46.3
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-3778Zero's internal tracking ID, independent of the CVE number., no cve assigned
cvss7.0ethiack provisional
23h 22msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+2.0d
0
+1d
+3d

description

Bindery deployments using tenancy enforcement are affected when user-role accounts exist. A user may be able to view book information belonging to other accounts and, in some shared-author cases, alter properties of other accounts' books. Deployments without tenancy enforcement do not use account boundaries for these libraries.

mitigation

Upgrade Bindery to version 1.46.3 or later. Until upgraded, assign untrusted accounts the requester role rather than the user role.

fixed in 1.46.3

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
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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-11-05 02:10Z

this entry in the feed

GET /api/v1/feed/ETK-2026-3778

{
  "etk_id": "ETK-2026-3778",
  "cve_id": null,
  "display_id": "ETK-2026-3778",
  "ghsa_id": "GHSA-q8wp-7gh7-4873",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cross-tenant authorization flaws in bindery",
  "summary": "Bindery deployments using tenancy enforcement are affected when user-role accounts exist. A user may be able to view book information belonging to other accounts and, in some shared-author cases, alter properties of other accounts' books. Deployments without tenancy enforcement do not use account boundaries for these libraries.",
  "mitigation": "Upgrade Bindery to version 1.46.3 or later. Until upgraded, assign untrusted accounts the requester role rather than the user role.",
  "vendor": "other",
  "product": "other:bindery",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.46.2"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "1.46.3"
      ],
      "package_name": "bindery",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.935526983333332,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T02:10:07+00:00",
      "days": -2.938924640347222,
      "is_lower_bound": true,
      "measured_at": "2026-11-08T00:42:10.177708+00:00",
      "url": "https://github.com/vavallee/bindery/security/advisories/GHSA-q8wp-7gh7-4873"
    }
  }
}

published 2026-11-07 01:14Z
last change 2026-11-08 00:40Z

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.