CVE-2026-126815

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

GHSA-f39m-86jx-7p47 ↗EUVD-2026-123800 ↗

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.
XauenDevs Lagarto Chivato >= 0.1.0, <= 0.4.2
CWE-287 Improper Authentication
ETK-2026-4213Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 17msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h28m
+2h
+4h
+6h
+8h
+10h
+12h

description

Lagarto Chivato 0.4.1 and earlier on Web has an authentication-flow flaw affecting accounts associated with previously unregistered email addresses. An unauthenticated attacker may take over such an account by establishing a password before the legitimate user first signs in through the passwordless flow. Exploitation requires the targeted email address to be unregistered when the attacker acts and later activated through an initial passwordless login.

mitigation

Disable or restrict password creation for unregistered email addresses, and require ownership verification before a password can be set or an account is activated. Review accounts created through the affected passwordless flow for unexpected passwords or ownership changes.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 20:10Z
Δ 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-11 20:10Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4213",
  "cve_id": "CVE-2026-126815",
  "display_id": "CVE-2026-126815",
  "ghsa_id": "GHSA-f39m-86jx-7p47",
  "euvd_id": "EUVD-2026-123800",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Pre-account hijacking in Lagarto Chivato authentication",
  "summary": "Lagarto Chivato 0.4.1 and earlier on Web has an authentication-flow flaw affecting accounts associated with previously unregistered email addresses. An unauthenticated attacker may take over such an account by establishing a password before the legitimate user first signs in through the passwordless flow. Exploitation requires the targeted email address to be unregistered when the attacker acts and later activated through an initial passwordless login.",
  "mitigation": "Disable or restrict password creation for unregistered email addresses, and require ownership verification before a password can be set or an account is activated. Review accounts created through the affected passwordless flow for unexpected passwords or ownership changes.",
  "vendor": "XauenDevs",
  "product": "Lagarto Chivato",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.1.0, <= 0.4.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Lagarto Chivato",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.686436366666667,
  "t0_at": "2026-11-11T20:10:36.118000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T20:10:36.118000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T20:10:36.118000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-126815"
    }
  }
}

published 2026-11-11 20:24Z
last change 2026-11-11 21:19Z

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.