CVE-2026-127111

validatedZero produced an exploit or a check.

GHSA-j27v-488j-289h ↗EUVD-2026-124528 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Alinto sogo < 5.12.13
fixed in 5.12.13
ETK-2026-4318Zero's internal tracking ID, independent of the CVE number., permanent identifier
+5h23mTTV
27mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+5h23magent stopped
0
+2h
+4h
+6h

description

SOGo versions before 5.12.13 do not sufficiently limit password-recovery answer attempts. An unauthenticated attacker who can guess an account's recovery answer may reset its password and access the account when TOTP is not enabled.

mitigation

Upgrade SOGo to version 5.12.13 or later. Require TOTP for accounts where possible while the upgrade is being deployed.

fixed in 5.12.13

check
available
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
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 15:53Z
Δ 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 check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

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

  1. 2026-11-12 15:53Z
    ghsa: trigger signal, started the run
  2. 2026-11-12 15:53Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4318",
  "cve_id": "CVE-2026-127111",
  "display_id": "CVE-2026-127111",
  "ghsa_id": "GHSA-j27v-488j-289h",
  "euvd_id": "EUVD-2026-124528",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SOGo password recovery brute-force protection failure",
  "summary": "SOGo versions before 5.12.13 do not sufficiently limit password-recovery answer attempts. An unauthenticated attacker who can guess an account's recovery answer may reset its password and access the account when TOTP is not enabled.",
  "mitigation": "Upgrade SOGo to version 5.12.13 or later. Require TOTP for accounts where possible while the upgrade is being deployed.",
  "vendor": "Alinto",
  "product": "sogo",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 5.12.13"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "5.12.13"
      ],
      "package_name": "sogo",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 27.288334233333334,
  "t0_at": "2026-11-12T15:53:16.849000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-12T21:15:59.755914+00:00",
      "days": 0.22410771891203704,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T15:53:16.849000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-12T15:53:16.849000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T15:53:16.849000+00:00",
      "url": "https://github.com/advisories/GHSA-j27v-488j-289h"
    }
  }
}

published 2026-11-12 20:48Z
last change 2026-11-13 03:49Z

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.